.. _LE1VisRawFrame: Vis Raw Frame Product --------------------- Data product name ================= .. DataProductNameStart DpdVisRawFrame .. DataProductNameEnd Data product custodian ====================== .. DataProductCustodianStart .. DataProductCustodianEnd Name of the Schema file ======================= .. NameSchemaStart .. raw:: html euc-le1-VisRawFrame.xsd .. NameSchemaEnd DPDD version ============ .. DpddVersionlTagStart 1.1 .. DpddVersionlTagEnd Processing Element(s) creating/using the data product ===================================================== .. PECreatorStart Creators: * LE1_VIS Consumers: * VIS_PF .. PECreatorEnd Processing function using the data product ========================================== .. PFUsingStart VIS processing function. .. PFUsingEnd Data product elements ===================== .. DataProductElementsStart :Header: object of type sys:genericHeader :Data: object of type le1vis:visRawFrame :QualityFlags: object of type dqc:sqfPlaceHolder :Parameters: object of type ppr:genericKeyValueParameters .. DataProductElementsEnd Detailed description of the data product ======================================== .. DetailedDescStart .. Comment by Editor (MS): I have significantly changed the use of the figure directive, and introduced markup for references instead of explicit references. This way figure numbering is consistent throughout the document. The LE1-VIS component of the LE1 processing function provides calibration and scientific exposures and the associated metadata. Calibration and scientific exposure is provided as one multi-extension FITS (MEF) file, with one extension per quadrant, that is 144 extensions altogether. The CCD numbering and location on the detector plane is showed on :numref:`CCDnumbering` and :numref:`CCDorganisation` below. The dotted circles are attachements of the CDD packages. .. _CCDnumbering: .. figure:: images/CCD_numbering.png :scale: 100 % :align: center :figclass: align-center : CCD numbering and location at detector plane level (Front view) From VIS FPA ICD (EUCL-SAP-ICD-6-001) issue 2.5 2014/20/10 .. _CCDorganisation: .. figure:: images/CCD_organisation.png :scale: 100 % :align: center :figclass: align-center : CCD numbering and location at detector plane level (Front view) From VIS FPA ICD (EUCL-SAP-ICD-6-001) issue 5.1 2020/10/23 One can notice that CCDs on the right side of the focal plane are rotated by 180° with respect to those on the left. This means that CCD quadrants are not positioned the same way across the FPA, as showed on the :numref:`quadPosFPA` below for CCD 1-3 and 1-4. .. _quadPosFPA: .. figure:: images/Quadrant_position.png :align: center :figclass: align-center :scale: 100 % : Quadrant position on the FPA :numref:`quadOrgCCD` below shows one CCD with the position of the 51 pre-scan and 20 over-scan pixels with respect to the imaging area. Each quadrant is marked with either E, F, G or H, according to the naming used by the manufacturer. .. _quadOrgCCD: .. figure:: images/Quadrant_organisation.png :scale: 50 % :align: center :figclass: align-center : Quadrant organisation in a CCD *Note: the charge injection structure which is four rows in the middle of the CCD: this will create a gap in the images.* Data encoding ************* All pixel data are in units of ADU, 16-bit unsigned integer. The origin of each data array is located at the bottom left of the FPA with respect to :numref:`CCDnumbering`. The following :numref:`FITSOrg` shows the origin of the data array and NAXIS1, NAXIS2 axes for each quadrant in a CCD. .. _FITSOrg: .. figure:: images/FITS_data_array_organisation.png :scale: 50 % :align: center :figclass: align-center : FITS data array organisation for each quadrant in a CCD Header content ************** **Primary header** **Extension headers** Each extension shall contain the CCD and quadrant identification. CCD will be identified with the numbering shown above (‘1-1’, ‘1-2’,..., ‘6-6’) and the quadrant by the letters ‘E’, ‘F’, ‘G’ or ‘H’ according to :numref:`quadOrgCCD`. On the next LE1 PF release, these two keywords value will be modified or added: #. Predicted / instantaneous spacecraft velocities in TBD referential: The spacecraft instantaneous velocity will be used to correct the velocity aberration (astrometric effect which produces an apparent displacement of celestial objects about their true positions, dependent on the velocity of the observer). In case the instantaneous spacecraft velocities were not available in time to be included in the LE1 data product we would use a predicted velocity to apply a first approximative correction that will be refined afterwards with the instantaneous value. #. Temperatur of the CCD check with VIS IDT that this data is available as such (which temperature sensors are there, which data will be available on ground?). #. Temperature of the telescope. #. File checksum. .. DetailedDescEnd