GET https://dev.normadoc.fr/_partial/cart/summary?template=%40SyliusShop%2FCart%2F_widget.html.twig

Response
200 OK
IP
216.73.217.22
Profiled on
Token
721a4b

Components

3 Twig Components
5 Render Count
3 ms Render Time
310.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		2 0.68ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		2 1.85ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.31ms

Render calls

ProductState App\Twig\Components\ProductState 310.0 MiB 0.43 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7309
    #id: 8734
    #code: "IEEE00000935"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751037665 {#7274
      date: 2025-06-27 17:21:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 29945
        #name: "IEEE 683:1976 (R2006)"
        #slug: "ieee-683-1976-r2006-ieee00000935-240386"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          The recommended block-transfer algorithms are discussed, and those given in the basic CAMAC specification are described. These algorithms are well established and are supported by existing hardware. Some new algorithms are then discussed. Compatibility, hardware design, and software considerations are addressed.<br />\n
          \t\t\t\t<br />\n
          The basic CAMAC specification (see Ref [1]) defines a single CAMAC operation as the activity which oc curs in response to a single CAMAC command. This activity may consist of the transfer of a single data word bet ween a CAMAC module and computer memory or the changing of the status of a module [for example, F (26), F (24)] or return of a value for Q as the result of a test made on the module, or any compatible set of the previously named activities. A block transfer is defined as a sequence of single CAMAC operations involving data which the user specifies by a command said to be of a higher level than one which specifies a single CAMAC operation. The higher level command contains all the information required for the specification of the desired sequence of single CAMAC command s and is interpreted by a channel which governs the activity on the CAMAC highway. Control information such as the readiness of the computer to participate in a data transfer, the state of the CAMAC Q line and the state of certain LAMs (Look-at-Me’s) or special synchronizing signals must be made available to the channel. The use made of the control information by the channel defines the block-transfer mode. If a module is to influence the sequence of ope rations within a block transfer, then it must have the features required by the algorithm.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Block Transfers in CAMAC Systems (Computer Automated Measurement and Control)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1580425200 {#7292
      date: 2020-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @215391600 {#7318
      date: 1976-10-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1143669600 {#7316
      date: 2006-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1573081200 {#7315
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "683"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#93009
  +product: App\Entity\Product\Product {#7309
    #id: 8734
    #code: "IEEE00000935"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751037665 {#7274
      date: 2025-06-27 17:21:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 29945
        #name: "IEEE 683:1976 (R2006)"
        #slug: "ieee-683-1976-r2006-ieee00000935-240386"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          The recommended block-transfer algorithms are discussed, and those given in the basic CAMAC specification are described. These algorithms are well established and are supported by existing hardware. Some new algorithms are then discussed. Compatibility, hardware design, and software considerations are addressed.<br />\n
          \t\t\t\t<br />\n
          The basic CAMAC specification (see Ref [1]) defines a single CAMAC operation as the activity which oc curs in response to a single CAMAC command. This activity may consist of the transfer of a single data word bet ween a CAMAC module and computer memory or the changing of the status of a module [for example, F (26), F (24)] or return of a value for Q as the result of a test made on the module, or any compatible set of the previously named activities. A block transfer is defined as a sequence of single CAMAC operations involving data which the user specifies by a command said to be of a higher level than one which specifies a single CAMAC operation. The higher level command contains all the information required for the specification of the desired sequence of single CAMAC command s and is interpreted by a channel which governs the activity on the CAMAC highway. Control information such as the readiness of the computer to participate in a data transfer, the state of the CAMAC Q line and the state of certain LAMs (Look-at-Me’s) or special synchronizing signals must be made available to the channel. The use made of the control information by the channel defines the block-transfer mode. If a module is to influence the sequence of ope rations within a block transfer, then it must have the features required by the algorithm.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Block Transfers in CAMAC Systems (Computer Automated Measurement and Control)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1580425200 {#7292
      date: 2020-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @215391600 {#7318
      date: 1976-10-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1143669600 {#7316
      date: 2006-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1573081200 {#7315
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "683"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 310.0 MiB 0.31 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7309
    #id: 8734
    #code: "IEEE00000935"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751037665 {#7274
      date: 2025-06-27 17:21:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 29945
        #name: "IEEE 683:1976 (R2006)"
        #slug: "ieee-683-1976-r2006-ieee00000935-240386"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          The recommended block-transfer algorithms are discussed, and those given in the basic CAMAC specification are described. These algorithms are well established and are supported by existing hardware. Some new algorithms are then discussed. Compatibility, hardware design, and software considerations are addressed.<br />\n
          \t\t\t\t<br />\n
          The basic CAMAC specification (see Ref [1]) defines a single CAMAC operation as the activity which oc curs in response to a single CAMAC command. This activity may consist of the transfer of a single data word bet ween a CAMAC module and computer memory or the changing of the status of a module [for example, F (26), F (24)] or return of a value for Q as the result of a test made on the module, or any compatible set of the previously named activities. A block transfer is defined as a sequence of single CAMAC operations involving data which the user specifies by a command said to be of a higher level than one which specifies a single CAMAC operation. The higher level command contains all the information required for the specification of the desired sequence of single CAMAC command s and is interpreted by a channel which governs the activity on the CAMAC highway. Control information such as the readiness of the computer to participate in a data transfer, the state of the CAMAC Q line and the state of certain LAMs (Look-at-Me’s) or special synchronizing signals must be made available to the channel. The use made of the control information by the channel defines the block-transfer mode. If a module is to influence the sequence of ope rations within a block transfer, then it must have the features required by the algorithm.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Block Transfers in CAMAC Systems (Computer Automated Measurement and Control)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1580425200 {#7292
      date: 2020-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @215391600 {#7318
      date: 1976-10-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1143669600 {#7316
      date: 2006-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1573081200 {#7315
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "683"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93202
  +product: App\Entity\Product\Product {#7309
    #id: 8734
    #code: "IEEE00000935"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751037665 {#7274
      date: 2025-06-27 17:21:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 29945
        #name: "IEEE 683:1976 (R2006)"
        #slug: "ieee-683-1976-r2006-ieee00000935-240386"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          The recommended block-transfer algorithms are discussed, and those given in the basic CAMAC specification are described. These algorithms are well established and are supported by existing hardware. Some new algorithms are then discussed. Compatibility, hardware design, and software considerations are addressed.<br />\n
          \t\t\t\t<br />\n
          The basic CAMAC specification (see Ref [1]) defines a single CAMAC operation as the activity which oc curs in response to a single CAMAC command. This activity may consist of the transfer of a single data word bet ween a CAMAC module and computer memory or the changing of the status of a module [for example, F (26), F (24)] or return of a value for Q as the result of a test made on the module, or any compatible set of the previously named activities. A block transfer is defined as a sequence of single CAMAC operations involving data which the user specifies by a command said to be of a higher level than one which specifies a single CAMAC operation. The higher level command contains all the information required for the specification of the desired sequence of single CAMAC command s and is interpreted by a channel which governs the activity on the CAMAC highway. Control information such as the readiness of the computer to participate in a data transfer, the state of the CAMAC Q line and the state of certain LAMs (Look-at-Me’s) or special synchronizing signals must be made available to the channel. The use made of the control information by the channel defines the block-transfer mode. If a module is to influence the sequence of ope rations within a block transfer, then it must have the features required by the algorithm.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Block Transfers in CAMAC Systems (Computer Automated Measurement and Control)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1580425200 {#7292
      date: 2020-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @215391600 {#7318
      date: 1976-10-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1143669600 {#7316
      date: 2006-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1573081200 {#7315
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "683"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 310.0 MiB 1.00 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7309
    #id: 8734
    #code: "IEEE00000935"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751037665 {#7274
      date: 2025-06-27 17:21:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 29945
        #name: "IEEE 683:1976 (R2006)"
        #slug: "ieee-683-1976-r2006-ieee00000935-240386"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          The recommended block-transfer algorithms are discussed, and those given in the basic CAMAC specification are described. These algorithms are well established and are supported by existing hardware. Some new algorithms are then discussed. Compatibility, hardware design, and software considerations are addressed.<br />\n
          \t\t\t\t<br />\n
          The basic CAMAC specification (see Ref [1]) defines a single CAMAC operation as the activity which oc curs in response to a single CAMAC command. This activity may consist of the transfer of a single data word bet ween a CAMAC module and computer memory or the changing of the status of a module [for example, F (26), F (24)] or return of a value for Q as the result of a test made on the module, or any compatible set of the previously named activities. A block transfer is defined as a sequence of single CAMAC operations involving data which the user specifies by a command said to be of a higher level than one which specifies a single CAMAC operation. The higher level command contains all the information required for the specification of the desired sequence of single CAMAC command s and is interpreted by a channel which governs the activity on the CAMAC highway. Control information such as the readiness of the computer to participate in a data transfer, the state of the CAMAC Q line and the state of certain LAMs (Look-at-Me’s) or special synchronizing signals must be made available to the channel. The use made of the control information by the channel defines the block-transfer mode. If a module is to influence the sequence of ope rations within a block transfer, then it must have the features required by the algorithm.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Block Transfers in CAMAC Systems (Computer Automated Measurement and Control)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1580425200 {#7292
      date: 2020-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @215391600 {#7318
      date: 1976-10-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1143669600 {#7316
      date: 2006-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1573081200 {#7315
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "683"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93277
  +product: App\Entity\Product\Product {#7309
    #id: 8734
    #code: "IEEE00000935"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751037665 {#7274
      date: 2025-06-27 17:21:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 29945
        #name: "IEEE 683:1976 (R2006)"
        #slug: "ieee-683-1976-r2006-ieee00000935-240386"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          The recommended block-transfer algorithms are discussed, and those given in the basic CAMAC specification are described. These algorithms are well established and are supported by existing hardware. Some new algorithms are then discussed. Compatibility, hardware design, and software considerations are addressed.<br />\n
          \t\t\t\t<br />\n
          The basic CAMAC specification (see Ref [1]) defines a single CAMAC operation as the activity which oc curs in response to a single CAMAC command. This activity may consist of the transfer of a single data word bet ween a CAMAC module and computer memory or the changing of the status of a module [for example, F (26), F (24)] or return of a value for Q as the result of a test made on the module, or any compatible set of the previously named activities. A block transfer is defined as a sequence of single CAMAC operations involving data which the user specifies by a command said to be of a higher level than one which specifies a single CAMAC operation. The higher level command contains all the information required for the specification of the desired sequence of single CAMAC command s and is interpreted by a channel which governs the activity on the CAMAC highway. Control information such as the readiness of the computer to participate in a data transfer, the state of the CAMAC Q line and the state of certain LAMs (Look-at-Me’s) or special synchronizing signals must be made available to the channel. The use made of the control information by the channel defines the block-transfer mode. If a module is to influence the sequence of ope rations within a block transfer, then it must have the features required by the algorithm.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Block Transfers in CAMAC Systems (Computer Automated Measurement and Control)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1580425200 {#7292
      date: 2020-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @215391600 {#7318
      date: 1976-10-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1143669600 {#7316
      date: 2006-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1573081200 {#7315
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "683"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 310.0 MiB 0.25 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7309
    #id: 8734
    #code: "IEEE00000935"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751037665 {#7274
      date: 2025-06-27 17:21:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 29945
        #name: "IEEE 683:1976 (R2006)"
        #slug: "ieee-683-1976-r2006-ieee00000935-240386"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          The recommended block-transfer algorithms are discussed, and those given in the basic CAMAC specification are described. These algorithms are well established and are supported by existing hardware. Some new algorithms are then discussed. Compatibility, hardware design, and software considerations are addressed.<br />\n
          \t\t\t\t<br />\n
          The basic CAMAC specification (see Ref [1]) defines a single CAMAC operation as the activity which oc curs in response to a single CAMAC command. This activity may consist of the transfer of a single data word bet ween a CAMAC module and computer memory or the changing of the status of a module [for example, F (26), F (24)] or return of a value for Q as the result of a test made on the module, or any compatible set of the previously named activities. A block transfer is defined as a sequence of single CAMAC operations involving data which the user specifies by a command said to be of a higher level than one which specifies a single CAMAC operation. The higher level command contains all the information required for the specification of the desired sequence of single CAMAC command s and is interpreted by a channel which governs the activity on the CAMAC highway. Control information such as the readiness of the computer to participate in a data transfer, the state of the CAMAC Q line and the state of certain LAMs (Look-at-Me’s) or special synchronizing signals must be made available to the channel. The use made of the control information by the channel defines the block-transfer mode. If a module is to influence the sequence of ope rations within a block transfer, then it must have the features required by the algorithm.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Block Transfers in CAMAC Systems (Computer Automated Measurement and Control)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1580425200 {#7292
      date: 2020-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @215391600 {#7318
      date: 1976-10-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1143669600 {#7316
      date: 2006-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1573081200 {#7315
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "683"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#100206
  +product: App\Entity\Product\Product {#7309
    #id: 8734
    #code: "IEEE00000935"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751037665 {#7274
      date: 2025-06-27 17:21:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 29945
        #name: "IEEE 683:1976 (R2006)"
        #slug: "ieee-683-1976-r2006-ieee00000935-240386"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          The recommended block-transfer algorithms are discussed, and those given in the basic CAMAC specification are described. These algorithms are well established and are supported by existing hardware. Some new algorithms are then discussed. Compatibility, hardware design, and software considerations are addressed.<br />\n
          \t\t\t\t<br />\n
          The basic CAMAC specification (see Ref [1]) defines a single CAMAC operation as the activity which oc curs in response to a single CAMAC command. This activity may consist of the transfer of a single data word bet ween a CAMAC module and computer memory or the changing of the status of a module [for example, F (26), F (24)] or return of a value for Q as the result of a test made on the module, or any compatible set of the previously named activities. A block transfer is defined as a sequence of single CAMAC operations involving data which the user specifies by a command said to be of a higher level than one which specifies a single CAMAC operation. The higher level command contains all the information required for the specification of the desired sequence of single CAMAC command s and is interpreted by a channel which governs the activity on the CAMAC highway. Control information such as the readiness of the computer to participate in a data transfer, the state of the CAMAC Q line and the state of certain LAMs (Look-at-Me’s) or special synchronizing signals must be made available to the channel. The use made of the control information by the channel defines the block-transfer mode. If a module is to influence the sequence of ope rations within a block transfer, then it must have the features required by the algorithm.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Block Transfers in CAMAC Systems (Computer Automated Measurement and Control)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1580425200 {#7292
      date: 2020-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @215391600 {#7318
      date: 1976-10-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1143669600 {#7316
      date: 2006-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1573081200 {#7315
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "683"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 310.0 MiB 0.85 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7309
    #id: 8734
    #code: "IEEE00000935"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751037665 {#7274
      date: 2025-06-27 17:21:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 29945
        #name: "IEEE 683:1976 (R2006)"
        #slug: "ieee-683-1976-r2006-ieee00000935-240386"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          The recommended block-transfer algorithms are discussed, and those given in the basic CAMAC specification are described. These algorithms are well established and are supported by existing hardware. Some new algorithms are then discussed. Compatibility, hardware design, and software considerations are addressed.<br />\n
          \t\t\t\t<br />\n
          The basic CAMAC specification (see Ref [1]) defines a single CAMAC operation as the activity which oc curs in response to a single CAMAC command. This activity may consist of the transfer of a single data word bet ween a CAMAC module and computer memory or the changing of the status of a module [for example, F (26), F (24)] or return of a value for Q as the result of a test made on the module, or any compatible set of the previously named activities. A block transfer is defined as a sequence of single CAMAC operations involving data which the user specifies by a command said to be of a higher level than one which specifies a single CAMAC operation. The higher level command contains all the information required for the specification of the desired sequence of single CAMAC command s and is interpreted by a channel which governs the activity on the CAMAC highway. Control information such as the readiness of the computer to participate in a data transfer, the state of the CAMAC Q line and the state of certain LAMs (Look-at-Me’s) or special synchronizing signals must be made available to the channel. The use made of the control information by the channel defines the block-transfer mode. If a module is to influence the sequence of ope rations within a block transfer, then it must have the features required by the algorithm.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Block Transfers in CAMAC Systems (Computer Automated Measurement and Control)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1580425200 {#7292
      date: 2020-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @215391600 {#7318
      date: 1976-10-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1143669600 {#7316
      date: 2006-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1573081200 {#7315
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "683"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#100290
  +product: App\Entity\Product\Product {#7309
    #id: 8734
    #code: "IEEE00000935"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751037665 {#7274
      date: 2025-06-27 17:21:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 29945
        #name: "IEEE 683:1976 (R2006)"
        #slug: "ieee-683-1976-r2006-ieee00000935-240386"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          The recommended block-transfer algorithms are discussed, and those given in the basic CAMAC specification are described. These algorithms are well established and are supported by existing hardware. Some new algorithms are then discussed. Compatibility, hardware design, and software considerations are addressed.<br />\n
          \t\t\t\t<br />\n
          The basic CAMAC specification (see Ref [1]) defines a single CAMAC operation as the activity which oc curs in response to a single CAMAC command. This activity may consist of the transfer of a single data word bet ween a CAMAC module and computer memory or the changing of the status of a module [for example, F (26), F (24)] or return of a value for Q as the result of a test made on the module, or any compatible set of the previously named activities. A block transfer is defined as a sequence of single CAMAC operations involving data which the user specifies by a command said to be of a higher level than one which specifies a single CAMAC operation. The higher level command contains all the information required for the specification of the desired sequence of single CAMAC command s and is interpreted by a channel which governs the activity on the CAMAC highway. Control information such as the readiness of the computer to participate in a data transfer, the state of the CAMAC Q line and the state of certain LAMs (Look-at-Me’s) or special synchronizing signals must be made available to the channel. The use made of the control information by the channel defines the block-transfer mode. If a module is to influence the sequence of ope rations within a block transfer, then it must have the features required by the algorithm.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Block Transfers in CAMAC Systems (Computer Automated Measurement and Control)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1580425200 {#7292
      date: 2020-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @215391600 {#7318
      date: 1976-10-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1143669600 {#7316
      date: 2006-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1573081200 {#7315
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "683"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}