GET https://dev.normadoc.fr/_partial/products/cross-sell?limit=2&products=%5B10864%5D&template=%40SyliusShop%2FProduct%2FsimilarList.html.twig

Response
200 OK
IP
216.73.217.148
Profiled on
Token
7dd1da

Forms

  • sylius_add_to_cart
    • cartItem
    • _token

sylius_add_to_cart

Form type: 
"Sylius\Bundle\CoreBundle\Form\Type\Order\AddToCartType"

Errors

This form has no errors.

Default Data

Property Value
Model Format same as normalized format
Normalized Format 
Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#113697
  -cart: App\Entity\Order\Order {#13374 …}
  -cartItem: App\Entity\Order\OrderItem {#113685
    #id: null
    #order: null
    #quantity: 1
    #unitPrice: 0
    #originalUnitPrice: 0
    #total: 0
    #immutable: false
    #units: Doctrine\Common\Collections\ArrayCollection {#113709 …}
    #unitsTotal: 0
    #adjustments: Doctrine\Common\Collections\ArrayCollection {#113710 …}
    #adjustmentsTotal: 0
    #version: 1
    #variant: App\Entity\Product\ProductVariant {#8104
      #id: 5471
      #code: "IEEE00005202PDF"
      #product: App\Entity\Product\Product {#7311
        #id: 10864
        #code: "IEEE00005202"
        #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
        #variants: Doctrine\ORM\PersistentCollection {#7744 …}
        #options: Doctrine\ORM\PersistentCollection {#7916
          #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
          #initialized: true
          -snapshot: [ …4]
          -owner: App\Entity\Product\Product {#7311}
          -association: [ …21]
          -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
          -backRefFieldName: null
          -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#222997 …}
          -isDirty: false
        }
        #associations: Doctrine\ORM\PersistentCollection {#7900 …}
        #createdAt: DateTime @1751039331 {#7274
          date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
        }
        #updatedAt: DateTime @1754608190 {#7322
          date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
        }
        #enabled: true
        #translations: Doctrine\ORM\PersistentCollection {#7922 …}
        #translationsCache: [
          "en_US" => App\Entity\Product\ProductTranslation {#7921
            #locale: "en_US"
            #translatable: App\Entity\Product\Product {#7311}
            #id: 38465
            #name: "IEEE N42.45:2011"
            #slug: "ieee-n42-45-2011-ieee00005202-242516"
            #description: """
               - Active.<br />\n
              Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
              \t\t\t\t<br />\n
              This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
              Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
              """
            #metaKeywords: null
            #metaDescription: null
            #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
            -notes: "Active"
          }
        ]
        #currentLocale: "en_US"
        #currentTranslation: null
        #fallbackLocale: "en_US"
        #variantSelectionMethod: "match"
        #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
        #channels: Doctrine\ORM\PersistentCollection {#7628 …}
        #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
        #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
        #averageRating: 0.0
        #images: Doctrine\ORM\PersistentCollection {#7645 …}
        -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
        -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
        -apiLastModifiedAt: DateTime @1754517600 {#7317
          date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
        }
        -lastUpdatedAt: DateTime @1656367200 {#7292
          date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
        }
        -author: ""
        -publishedAt: DateTime @1306101600 {#7318
          date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
        }
        -releasedAt: null
        -confirmedAt: null
        -canceledAt: DateTime @1306101600 {#7316
          date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
        }
        -edition: null
        -coreDocument: "N42.45"
        -bookCollection: ""
        -pageCount: 58
        -documents: Doctrine\ORM\PersistentCollection {#7465 …}
        -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
      }
      #optionValues: Doctrine\ORM\PersistentCollection {#8320 …}
      #position: 0
      #createdAt: DateTime @1751041236 {#7283
        date: 2025-06-27 18:20:36.0 Europe/Paris (+02:00)
      }
      #updatedAt: DateTime @1755611995 {#8121
        date: 2025-08-19 15:59:55.0 Europe/Paris (+02:00)
      }
      #enabled: true
      #translations: Doctrine\ORM\PersistentCollection {#8264 …}
      #translationsCache: [
        "en_US" => App\Entity\Product\ProductVariantTranslation {#93381
          #locale: "en_US"
          #translatable: App\Entity\Product\ProductVariant {#8104}
          #id: 5501
          #name: null
          -shortDescription: null
          -description: null
          -notes: null
          -shippingInformation: "Instant download"
        }
      ]
      #currentLocale: "en_US"
      #currentTranslation: null
      #fallbackLocale: "en_US"
      #version: 9
      #onHold: 0
      #onHand: 0
      #tracked: false
      #weight: 0.0
      #width: null
      #height: null
      #depth: null
      #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8136 …}
      #shippingCategory: null
      #channelPricings: Doctrine\ORM\PersistentCollection {#8298 …}
      #shippingRequired: true
      #images: Doctrine\ORM\PersistentCollection {#8295 …}
      -apiLastModifiedAt: DateTime @1754517600 {#8103
        date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
      }
      -publishedAt: null
      -isbn: "978-0-7381-6651-3"
      -ean: "9780738166513"
      -numberOfUsers: 1
      -physicalProduct: false
      -downloadableImmediately: true
      -downloadable: true
      -drmViewerUrl: "https://online-viewer.normadoc.com/CGZbrQ"
      -sellable: true
      -documents: Doctrine\ORM\PersistentCollection {#8132 …}
      -drmTokens: Doctrine\ORM\PersistentCollection {#8124 …}
      -enabledForSubscribers: true
      -currentAreaContext: null
    }
    #productName: null
    #variantName: null
  }
}
View Format same as normalized format

Submitted Data

This form was not submitted.

Passed Options

Option Passed Value Resolved Value
data 
Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#113697
  -cart: App\Entity\Order\Order {#13374 …}
  -cartItem: App\Entity\Order\OrderItem {#113685
    #id: null
    #order: null
    #quantity: 1
    #unitPrice: 0
    #originalUnitPrice: 0
    #total: 0
    #immutable: false
    #units: Doctrine\Common\Collections\ArrayCollection {#113709 …}
    #unitsTotal: 0
    #adjustments: Doctrine\Common\Collections\ArrayCollection {#113710 …}
    #adjustmentsTotal: 0
    #version: 1
    #variant: App\Entity\Product\ProductVariant {#8104
      #id: 5471
      #code: "IEEE00005202PDF"
      #product: App\Entity\Product\Product {#7311
        #id: 10864
        #code: "IEEE00005202"
        #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
        #variants: Doctrine\ORM\PersistentCollection {#7744 …}
        #options: Doctrine\ORM\PersistentCollection {#7916
          #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
          #initialized: true
          -snapshot: [ …4]
          -owner: App\Entity\Product\Product {#7311}
          -association: [ …21]
          -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
          -backRefFieldName: null
          -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#222997 …}
          -isDirty: false
        }
        #associations: Doctrine\ORM\PersistentCollection {#7900 …}
        #createdAt: DateTime @1751039331 {#7274
          date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
        }
        #updatedAt: DateTime @1754608190 {#7322
          date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
        }
        #enabled: true
        #translations: Doctrine\ORM\PersistentCollection {#7922 …}
        #translationsCache: [
          "en_US" => App\Entity\Product\ProductTranslation {#7921
            #locale: "en_US"
            #translatable: App\Entity\Product\Product {#7311}
            #id: 38465
            #name: "IEEE N42.45:2011"
            #slug: "ieee-n42-45-2011-ieee00005202-242516"
            #description: """
               - Active.<br />\n
              Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
              \t\t\t\t<br />\n
              This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
              Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
              """
            #metaKeywords: null
            #metaDescription: null
            #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
            -notes: "Active"
          }
        ]
        #currentLocale: "en_US"
        #currentTranslation: null
        #fallbackLocale: "en_US"
        #variantSelectionMethod: "match"
        #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
        #channels: Doctrine\ORM\PersistentCollection {#7628 …}
        #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
        #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
        #averageRating: 0.0
        #images: Doctrine\ORM\PersistentCollection {#7645 …}
        -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
        -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
        -apiLastModifiedAt: DateTime @1754517600 {#7317
          date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
        }
        -lastUpdatedAt: DateTime @1656367200 {#7292
          date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
        }
        -author: ""
        -publishedAt: DateTime @1306101600 {#7318
          date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
        }
        -releasedAt: null
        -confirmedAt: null
        -canceledAt: DateTime @1306101600 {#7316
          date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
        }
        -edition: null
        -coreDocument: "N42.45"
        -bookCollection: ""
        -pageCount: 58
        -documents: Doctrine\ORM\PersistentCollection {#7465 …}
        -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
      }
      #optionValues: Doctrine\ORM\PersistentCollection {#8320 …}
      #position: 0
      #createdAt: DateTime @1751041236 {#7283
        date: 2025-06-27 18:20:36.0 Europe/Paris (+02:00)
      }
      #updatedAt: DateTime @1755611995 {#8121
        date: 2025-08-19 15:59:55.0 Europe/Paris (+02:00)
      }
      #enabled: true
      #translations: Doctrine\ORM\PersistentCollection {#8264 …}
      #translationsCache: [
        "en_US" => App\Entity\Product\ProductVariantTranslation {#93381
          #locale: "en_US"
          #translatable: App\Entity\Product\ProductVariant {#8104}
          #id: 5501
          #name: null
          -shortDescription: null
          -description: null
          -notes: null
          -shippingInformation: "Instant download"
        }
      ]
      #currentLocale: "en_US"
      #currentTranslation: null
      #fallbackLocale: "en_US"
      #version: 9
      #onHold: 0
      #onHand: 0
      #tracked: false
      #weight: 0.0
      #width: null
      #height: null
      #depth: null
      #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8136 …}
      #shippingCategory: null
      #channelPricings: Doctrine\ORM\PersistentCollection {#8298 …}
      #shippingRequired: true
      #images: Doctrine\ORM\PersistentCollection {#8295 …}
      -apiLastModifiedAt: DateTime @1754517600 {#8103
        date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
      }
      -publishedAt: null
      -isbn: "978-0-7381-6651-3"
      -ean: "9780738166513"
      -numberOfUsers: 1
      -physicalProduct: false
      -downloadableImmediately: true
      -downloadable: true
      -drmViewerUrl: "https://online-viewer.normadoc.com/CGZbrQ"
      -sellable: true
      -documents: Doctrine\ORM\PersistentCollection {#8132 …}
      -drmTokens: Doctrine\ORM\PersistentCollection {#8124 …}
      -enabledForSubscribers: true
      -currentAreaContext: null
    }
    #productName: null
    #variantName: null
  }
}
 same as passed value
product 
App\Entity\Product\Product {#7311
  #id: 10864
  #code: "IEEE00005202"
  #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
  #variants: Doctrine\ORM\PersistentCollection {#7744 …}
  #options: Doctrine\ORM\PersistentCollection {#7916
    #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
    #initialized: true
    -snapshot: [ …4]
    -owner: App\Entity\Product\Product {#7311}
    -association: [ …21]
    -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
    -backRefFieldName: null
    -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#222997 …}
    -isDirty: false
  }
  #associations: Doctrine\ORM\PersistentCollection {#7900 …}
  #createdAt: DateTime @1751039331 {#7274
    date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
  }
  #updatedAt: DateTime @1754608190 {#7322
    date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
  }
  #enabled: true
  #translations: Doctrine\ORM\PersistentCollection {#7922 …}
  #translationsCache: [
    "en_US" => App\Entity\Product\ProductTranslation {#7921
      #locale: "en_US"
      #translatable: App\Entity\Product\Product {#7311}
      #id: 38465
      #name: "IEEE N42.45:2011"
      #slug: "ieee-n42-45-2011-ieee00005202-242516"
      #description: """
         - Active.<br />\n
        Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
        \t\t\t\t<br />\n
        This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
        Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
        """
      #metaKeywords: null
      #metaDescription: null
      #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
      -notes: "Active"
    }
  ]
  #currentLocale: "en_US"
  #currentTranslation: null
  #fallbackLocale: "en_US"
  #variantSelectionMethod: "match"
  #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
  #channels: Doctrine\ORM\PersistentCollection {#7628 …}
  #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
  #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
  #averageRating: 0.0
  #images: Doctrine\ORM\PersistentCollection {#7645 …}
  -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
  -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
  -apiLastModifiedAt: DateTime @1754517600 {#7317
    date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
  }
  -lastUpdatedAt: DateTime @1656367200 {#7292
    date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
  }
  -author: ""
  -publishedAt: DateTime @1306101600 {#7318
    date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
  }
  -releasedAt: null
  -confirmedAt: null
  -canceledAt: DateTime @1306101600 {#7316
    date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
  }
  -edition: null
  -coreDocument: "N42.45"
  -bookCollection: ""
  -pageCount: 58
  -documents: Doctrine\ORM\PersistentCollection {#7465 …}
  -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
}
 same as passed value

Resolved Options

Option Value
action 
""
allow_extra_fields 
false
allow_file_upload 
false
attr 
[]
attr_translation_parameters 
[]
auto_initialize 
true
block_name 
null
block_prefix 
null
by_reference 
true
compound 
true
constraints 
[]
csrf_field_name 
"_token"
csrf_message 
"The CSRF token is invalid. Please try to resubmit the form."
csrf_protection 
true
csrf_token_id 
null
csrf_token_manager 
Symfony\Component\Security\Csrf\CsrfTokenManager {#113717
  -generator: Symfony\Component\Security\Csrf\TokenGenerator\UriSafeTokenGenerator {#113718 …}
  -storage: Symfony\Component\Security\Csrf\TokenStorage\SessionTokenStorage {#113719 …}
  -namespace: Closure() {#113721 …}
}
data 
Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#113697
  -cart: App\Entity\Order\Order {#13374 …}
  -cartItem: App\Entity\Order\OrderItem {#113685
    #id: null
    #order: null
    #quantity: 1
    #unitPrice: 0
    #originalUnitPrice: 0
    #total: 0
    #immutable: false
    #units: Doctrine\Common\Collections\ArrayCollection {#113709 …}
    #unitsTotal: 0
    #adjustments: Doctrine\Common\Collections\ArrayCollection {#113710 …}
    #adjustmentsTotal: 0
    #version: 1
    #variant: App\Entity\Product\ProductVariant {#8104
      #id: 5471
      #code: "IEEE00005202PDF"
      #product: App\Entity\Product\Product {#7311
        #id: 10864
        #code: "IEEE00005202"
        #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
        #variants: Doctrine\ORM\PersistentCollection {#7744 …}
        #options: Doctrine\ORM\PersistentCollection {#7916
          #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
          #initialized: true
          -snapshot: [ …4]
          -owner: App\Entity\Product\Product {#7311}
          -association: [ …21]
          -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
          -backRefFieldName: null
          -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#222997 …}
          -isDirty: false
        }
        #associations: Doctrine\ORM\PersistentCollection {#7900 …}
        #createdAt: DateTime @1751039331 {#7274
          date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
        }
        #updatedAt: DateTime @1754608190 {#7322
          date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
        }
        #enabled: true
        #translations: Doctrine\ORM\PersistentCollection {#7922 …}
        #translationsCache: [
          "en_US" => App\Entity\Product\ProductTranslation {#7921
            #locale: "en_US"
            #translatable: App\Entity\Product\Product {#7311}
            #id: 38465
            #name: "IEEE N42.45:2011"
            #slug: "ieee-n42-45-2011-ieee00005202-242516"
            #description: """
               - Active.<br />\n
              Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
              \t\t\t\t<br />\n
              This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
              Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
              """
            #metaKeywords: null
            #metaDescription: null
            #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
            -notes: "Active"
          }
        ]
        #currentLocale: "en_US"
        #currentTranslation: null
        #fallbackLocale: "en_US"
        #variantSelectionMethod: "match"
        #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
        #channels: Doctrine\ORM\PersistentCollection {#7628 …}
        #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
        #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
        #averageRating: 0.0
        #images: Doctrine\ORM\PersistentCollection {#7645 …}
        -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
        -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
        -apiLastModifiedAt: DateTime @1754517600 {#7317
          date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
        }
        -lastUpdatedAt: DateTime @1656367200 {#7292
          date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
        }
        -author: ""
        -publishedAt: DateTime @1306101600 {#7318
          date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
        }
        -releasedAt: null
        -confirmedAt: null
        -canceledAt: DateTime @1306101600 {#7316
          date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
        }
        -edition: null
        -coreDocument: "N42.45"
        -bookCollection: ""
        -pageCount: 58
        -documents: Doctrine\ORM\PersistentCollection {#7465 …}
        -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
      }
      #optionValues: Doctrine\ORM\PersistentCollection {#8320 …}
      #position: 0
      #createdAt: DateTime @1751041236 {#7283
        date: 2025-06-27 18:20:36.0 Europe/Paris (+02:00)
      }
      #updatedAt: DateTime @1755611995 {#8121
        date: 2025-08-19 15:59:55.0 Europe/Paris (+02:00)
      }
      #enabled: true
      #translations: Doctrine\ORM\PersistentCollection {#8264 …}
      #translationsCache: [
        "en_US" => App\Entity\Product\ProductVariantTranslation {#93381
          #locale: "en_US"
          #translatable: App\Entity\Product\ProductVariant {#8104}
          #id: 5501
          #name: null
          -shortDescription: null
          -description: null
          -notes: null
          -shippingInformation: "Instant download"
        }
      ]
      #currentLocale: "en_US"
      #currentTranslation: null
      #fallbackLocale: "en_US"
      #version: 9
      #onHold: 0
      #onHand: 0
      #tracked: false
      #weight: 0.0
      #width: null
      #height: null
      #depth: null
      #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8136 …}
      #shippingCategory: null
      #channelPricings: Doctrine\ORM\PersistentCollection {#8298 …}
      #shippingRequired: true
      #images: Doctrine\ORM\PersistentCollection {#8295 …}
      -apiLastModifiedAt: DateTime @1754517600 {#8103
        date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
      }
      -publishedAt: null
      -isbn: "978-0-7381-6651-3"
      -ean: "9780738166513"
      -numberOfUsers: 1
      -physicalProduct: false
      -downloadableImmediately: true
      -downloadable: true
      -drmViewerUrl: "https://online-viewer.normadoc.com/CGZbrQ"
      -sellable: true
      -documents: Doctrine\ORM\PersistentCollection {#8132 …}
      -drmTokens: Doctrine\ORM\PersistentCollection {#8124 …}
      -enabledForSubscribers: true
      -currentAreaContext: null
    }
    #productName: null
    #variantName: null
  }
}
data_class 
"Sylius\Bundle\OrderBundle\Controller\AddToCartCommand"
disabled 
false
empty_data 
Closure(FormInterface $form) {#113744
  class: "Symfony\Component\Form\Extension\Core\Type\FormType"
  use: {
    $class: "Sylius\Bundle\OrderBundle\Controller\AddToCartCommand"
  }
}
error_bubbling 
true
error_mapping 
[]
extra_fields_message 
"This form should not contain extra fields."
form_attr 
false
getter 
null
help 
null
help_attr 
[]
help_html 
false
help_translation_parameters 
[]
inherit_data 
false
invalid_message 
"This value is not valid."
invalid_message_parameters 
[]
is_empty_callback 
null
label 
null
label_attr 
[]
label_format 
null
label_html 
false
label_translation_parameters 
[]
mapped 
true
method 
"POST"
post_max_size_message 
"The uploaded file was too large. Please try to upload a smaller file."
priority 
0
product 
App\Entity\Product\Product {#7311
  #id: 10864
  #code: "IEEE00005202"
  #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
  #variants: Doctrine\ORM\PersistentCollection {#7744 …}
  #options: Doctrine\ORM\PersistentCollection {#7916
    #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
    #initialized: true
    -snapshot: [ …4]
    -owner: App\Entity\Product\Product {#7311}
    -association: [ …21]
    -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
    -backRefFieldName: null
    -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#222997 …}
    -isDirty: false
  }
  #associations: Doctrine\ORM\PersistentCollection {#7900 …}
  #createdAt: DateTime @1751039331 {#7274
    date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
  }
  #updatedAt: DateTime @1754608190 {#7322
    date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
  }
  #enabled: true
  #translations: Doctrine\ORM\PersistentCollection {#7922 …}
  #translationsCache: [
    "en_US" => App\Entity\Product\ProductTranslation {#7921
      #locale: "en_US"
      #translatable: App\Entity\Product\Product {#7311}
      #id: 38465
      #name: "IEEE N42.45:2011"
      #slug: "ieee-n42-45-2011-ieee00005202-242516"
      #description: """
         - Active.<br />\n
        Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
        \t\t\t\t<br />\n
        This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
        Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
        """
      #metaKeywords: null
      #metaDescription: null
      #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
      -notes: "Active"
    }
  ]
  #currentLocale: "en_US"
  #currentTranslation: null
  #fallbackLocale: "en_US"
  #variantSelectionMethod: "match"
  #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
  #channels: Doctrine\ORM\PersistentCollection {#7628 …}
  #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
  #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
  #averageRating: 0.0
  #images: Doctrine\ORM\PersistentCollection {#7645 …}
  -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
  -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
  -apiLastModifiedAt: DateTime @1754517600 {#7317
    date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
  }
  -lastUpdatedAt: DateTime @1656367200 {#7292
    date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
  }
  -author: ""
  -publishedAt: DateTime @1306101600 {#7318
    date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
  }
  -releasedAt: null
  -confirmedAt: null
  -canceledAt: DateTime @1306101600 {#7316
    date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
  }
  -edition: null
  -coreDocument: "N42.45"
  -bookCollection: ""
  -pageCount: 58
  -documents: Doctrine\ORM\PersistentCollection {#7465 …}
  -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
}
property_path 
null
required 
true
row_attr 
[]
setter 
null
translation_domain 
null
trim 
true
upload_max_size_message 
Closure() {#113746
  class: "Symfony\Component\Form\Extension\Validator\Type\UploadValidatorExtension"
  use: {
    $translator: Symfony\Component\Translation\DataCollectorTranslator {#2251 …}
    $message: Closure() {#113745 …}
    $translationDomain: "validators"
  }
}
validation_groups 
[
  "sylius"
]

View Vars

Variable Value
action 
""
attr 
[]
attr_translation_parameters 
[]
block_prefixes 
[
  "form"
  "sylius_add_to_cart"
  "_sylius_add_to_cart"
]
cache_key 
"_sylius_add_to_cart_sylius_add_to_cart"
compound 
true
data 
Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#113697
  -cart: App\Entity\Order\Order {#13374 …}
  -cartItem: App\Entity\Order\OrderItem {#113685
    #id: null
    #order: null
    #quantity: 1
    #unitPrice: 0
    #originalUnitPrice: 0
    #total: 0
    #immutable: false
    #units: Doctrine\Common\Collections\ArrayCollection {#113709 …}
    #unitsTotal: 0
    #adjustments: Doctrine\Common\Collections\ArrayCollection {#113710 …}
    #adjustmentsTotal: 0
    #version: 1
    #variant: App\Entity\Product\ProductVariant {#8104
      #id: 5471
      #code: "IEEE00005202PDF"
      #product: App\Entity\Product\Product {#7311
        #id: 10864
        #code: "IEEE00005202"
        #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
        #variants: Doctrine\ORM\PersistentCollection {#7744 …}
        #options: Doctrine\ORM\PersistentCollection {#7916
          #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
          #initialized: true
          -snapshot: [ …4]
          -owner: App\Entity\Product\Product {#7311}
          -association: [ …21]
          -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
          -backRefFieldName: null
          -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#222997 …}
          -isDirty: false
        }
        #associations: Doctrine\ORM\PersistentCollection {#7900 …}
        #createdAt: DateTime @1751039331 {#7274
          date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
        }
        #updatedAt: DateTime @1754608190 {#7322
          date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
        }
        #enabled: true
        #translations: Doctrine\ORM\PersistentCollection {#7922 …}
        #translationsCache: [
          "en_US" => App\Entity\Product\ProductTranslation {#7921
            #locale: "en_US"
            #translatable: App\Entity\Product\Product {#7311}
            #id: 38465
            #name: "IEEE N42.45:2011"
            #slug: "ieee-n42-45-2011-ieee00005202-242516"
            #description: """
               - Active.<br />\n
              Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
              \t\t\t\t<br />\n
              This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
              Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
              """
            #metaKeywords: null
            #metaDescription: null
            #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
            -notes: "Active"
          }
        ]
        #currentLocale: "en_US"
        #currentTranslation: null
        #fallbackLocale: "en_US"
        #variantSelectionMethod: "match"
        #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
        #channels: Doctrine\ORM\PersistentCollection {#7628 …}
        #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
        #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
        #averageRating: 0.0
        #images: Doctrine\ORM\PersistentCollection {#7645 …}
        -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
        -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
        -apiLastModifiedAt: DateTime @1754517600 {#7317
          date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
        }
        -lastUpdatedAt: DateTime @1656367200 {#7292
          date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
        }
        -author: ""
        -publishedAt: DateTime @1306101600 {#7318
          date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
        }
        -releasedAt: null
        -confirmedAt: null
        -canceledAt: DateTime @1306101600 {#7316
          date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
        }
        -edition: null
        -coreDocument: "N42.45"
        -bookCollection: ""
        -pageCount: 58
        -documents: Doctrine\ORM\PersistentCollection {#7465 …}
        -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
      }
      #optionValues: Doctrine\ORM\PersistentCollection {#8320 …}
      #position: 0
      #createdAt: DateTime @1751041236 {#7283
        date: 2025-06-27 18:20:36.0 Europe/Paris (+02:00)
      }
      #updatedAt: DateTime @1755611995 {#8121
        date: 2025-08-19 15:59:55.0 Europe/Paris (+02:00)
      }
      #enabled: true
      #translations: Doctrine\ORM\PersistentCollection {#8264 …}
      #translationsCache: [
        "en_US" => App\Entity\Product\ProductVariantTranslation {#93381
          #locale: "en_US"
          #translatable: App\Entity\Product\ProductVariant {#8104}
          #id: 5501
          #name: null
          -shortDescription: null
          -description: null
          -notes: null
          -shippingInformation: "Instant download"
        }
      ]
      #currentLocale: "en_US"
      #currentTranslation: null
      #fallbackLocale: "en_US"
      #version: 9
      #onHold: 0
      #onHand: 0
      #tracked: false
      #weight: 0.0
      #width: null
      #height: null
      #depth: null
      #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8136 …}
      #shippingCategory: null
      #channelPricings: Doctrine\ORM\PersistentCollection {#8298 …}
      #shippingRequired: true
      #images: Doctrine\ORM\PersistentCollection {#8295 …}
      -apiLastModifiedAt: DateTime @1754517600 {#8103
        date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
      }
      -publishedAt: null
      -isbn: "978-0-7381-6651-3"
      -ean: "9780738166513"
      -numberOfUsers: 1
      -physicalProduct: false
      -downloadableImmediately: true
      -downloadable: true
      -drmViewerUrl: "https://online-viewer.normadoc.com/CGZbrQ"
      -sellable: true
      -documents: Doctrine\ORM\PersistentCollection {#8132 …}
      -drmTokens: Doctrine\ORM\PersistentCollection {#8124 …}
      -enabledForSubscribers: true
      -currentAreaContext: null
    }
    #productName: null
    #variantName: null
  }
}
disabled 
false
errors 
Symfony\Component\Form\FormErrorIterator {#113771
  -form: Symfony\Component\Form\Form {#113776 …}
  -errors: []
}
form 
Symfony\Component\Form\FormView {#113747 …5}
full_name 
"sylius_add_to_cart"
help 
null
help_attr 
[]
help_html 
false
help_translation_parameters 
[]
id 
"sylius_add_to_cart"
label 
null
label_attr 
[]
label_format 
null
label_html 
false
label_translation_parameters 
[]
method 
"POST"
multipart 
false
name 
"sylius_add_to_cart"
priority 
0
required 
true
row_attr 
[]
submitted 
false
translation_domain 
null
unique_block_prefix 
"_sylius_add_to_cart"
valid 
true
value 
Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#113697
  -cart: App\Entity\Order\Order {#13374 …}
  -cartItem: App\Entity\Order\OrderItem {#113685
    #id: null
    #order: null
    #quantity: 1
    #unitPrice: 0
    #originalUnitPrice: 0
    #total: 0
    #immutable: false
    #units: Doctrine\Common\Collections\ArrayCollection {#113709 …}
    #unitsTotal: 0
    #adjustments: Doctrine\Common\Collections\ArrayCollection {#113710 …}
    #adjustmentsTotal: 0
    #version: 1
    #variant: App\Entity\Product\ProductVariant {#8104
      #id: 5471
      #code: "IEEE00005202PDF"
      #product: App\Entity\Product\Product {#7311
        #id: 10864
        #code: "IEEE00005202"
        #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
        #variants: Doctrine\ORM\PersistentCollection {#7744 …}
        #options: Doctrine\ORM\PersistentCollection {#7916
          #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
          #initialized: true
          -snapshot: [ …4]
          -owner: App\Entity\Product\Product {#7311}
          -association: [ …21]
          -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
          -backRefFieldName: null
          -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#222997 …}
          -isDirty: false
        }
        #associations: Doctrine\ORM\PersistentCollection {#7900 …}
        #createdAt: DateTime @1751039331 {#7274
          date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
        }
        #updatedAt: DateTime @1754608190 {#7322
          date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
        }
        #enabled: true
        #translations: Doctrine\ORM\PersistentCollection {#7922 …}
        #translationsCache: [
          "en_US" => App\Entity\Product\ProductTranslation {#7921
            #locale: "en_US"
            #translatable: App\Entity\Product\Product {#7311}
            #id: 38465
            #name: "IEEE N42.45:2011"
            #slug: "ieee-n42-45-2011-ieee00005202-242516"
            #description: """
               - Active.<br />\n
              Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
              \t\t\t\t<br />\n
              This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
              Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
              """
            #metaKeywords: null
            #metaDescription: null
            #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
            -notes: "Active"
          }
        ]
        #currentLocale: "en_US"
        #currentTranslation: null
        #fallbackLocale: "en_US"
        #variantSelectionMethod: "match"
        #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
        #channels: Doctrine\ORM\PersistentCollection {#7628 …}
        #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
        #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
        #averageRating: 0.0
        #images: Doctrine\ORM\PersistentCollection {#7645 …}
        -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
        -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
        -apiLastModifiedAt: DateTime @1754517600 {#7317
          date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
        }
        -lastUpdatedAt: DateTime @1656367200 {#7292
          date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
        }
        -author: ""
        -publishedAt: DateTime @1306101600 {#7318
          date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
        }
        -releasedAt: null
        -confirmedAt: null
        -canceledAt: DateTime @1306101600 {#7316
          date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
        }
        -edition: null
        -coreDocument: "N42.45"
        -bookCollection: ""
        -pageCount: 58
        -documents: Doctrine\ORM\PersistentCollection {#7465 …}
        -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
      }
      #optionValues: Doctrine\ORM\PersistentCollection {#8320 …}
      #position: 0
      #createdAt: DateTime @1751041236 {#7283
        date: 2025-06-27 18:20:36.0 Europe/Paris (+02:00)
      }
      #updatedAt: DateTime @1755611995 {#8121
        date: 2025-08-19 15:59:55.0 Europe/Paris (+02:00)
      }
      #enabled: true
      #translations: Doctrine\ORM\PersistentCollection {#8264 …}
      #translationsCache: [
        "en_US" => App\Entity\Product\ProductVariantTranslation {#93381
          #locale: "en_US"
          #translatable: App\Entity\Product\ProductVariant {#8104}
          #id: 5501
          #name: null
          -shortDescription: null
          -description: null
          -notes: null
          -shippingInformation: "Instant download"
        }
      ]
      #currentLocale: "en_US"
      #currentTranslation: null
      #fallbackLocale: "en_US"
      #version: 9
      #onHold: 0
      #onHand: 0
      #tracked: false
      #weight: 0.0
      #width: null
      #height: null
      #depth: null
      #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8136 …}
      #shippingCategory: null
      #channelPricings: Doctrine\ORM\PersistentCollection {#8298 …}
      #shippingRequired: true
      #images: Doctrine\ORM\PersistentCollection {#8295 …}
      -apiLastModifiedAt: DateTime @1754517600 {#8103
        date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
      }
      -publishedAt: null
      -isbn: "978-0-7381-6651-3"
      -ean: "9780738166513"
      -numberOfUsers: 1
      -physicalProduct: false
      -downloadableImmediately: true
      -downloadable: true
      -drmViewerUrl: "https://online-viewer.normadoc.com/CGZbrQ"
      -sellable: true
      -documents: Doctrine\ORM\PersistentCollection {#8132 …}
      -drmTokens: Doctrine\ORM\PersistentCollection {#8124 …}
      -enabledForSubscribers: true
      -currentAreaContext: null
    }
    #productName: null
    #variantName: null
  }
}