The eclairs-gp team at APC/IN2P3
Last modification: mercredi 2 mars 2022, 10:04:40 (UTC+0100)
============================================================================

This directory contains several runtime files for testing 'eclairs-gp' pipeline
'out-of-the-box'. Some files concern elements for the testing files in
eclairs-gp. Other files comes from the "Eclairs's Calibration DataBase" (CalDB)
created by the "Eclairs Intrument Center" at IRAP in Toulouse (EIC/IRAP) and
wa have a 'local' copy as default for runtime tests.


Content
============================================================================
 comput 3625920 dec.   3  2019 ECL-EVT-SEC_Crab_CXBflat_50s_105chan.fits
 comput   74880 dec.   9 23:32 ECL-PIX-CAL_2021-01-01_00:00:00.fits
 comput   74880 dec.   9 23:32 ECL-PIX-CAL_20210130T01.fits
 comput   25920 nov.  22 11:26 ECL-RSP-ARF_2021-10-12_13:13:00.fits
 comput   25920 nov.  22 11:26 ECL-RSP-ARF_20211023T01.fits
 comput 8118720 nov.  22 11:26 ECL-RSP-IRF_20210130T01.fits
 comput  653760 mars   1 15:52 ECL-RSP-IRF_2021-10-11_09:06:00.fits
 comput  653760 mars   1 15:52 ECL-RSP-IRF_20211011T01.fits
 comput 8118720 nov.  22 11:26 ECL-RSP-RMF_2021-10-13_10:36:00.fits
 comput    4096 oct.  25  2019 grb
 comput    4096 oct.  25  2019 images
 comput    4096 mars   1 15:54 old
 comput    4096 nov.  22 11:36 pytest
 comput    5555 mars   2 10:05 README
 comput    4096 mars   2 10:07 .README.swp
 comput    8640 dec.   3  2019 SVO-ATT-CNV-UTC18581117T000000.fits
 comput    4096 nov.   8  2019 video


CalDB files 
=============================================================================
CalDB files follows a naming convention described in section 6 of the internal
document EIC-SN-A32-022-IRAP.


Extract from the Reference document
EIC-SN-A32-022-IRAP, Ed.:2, Rev.:0 on 2019/11/26 pp 11/67
==============================================================================
6. NAMING OF FITS FILES

We follow the convention described in the document Note on versioning of CAL
tables (https://forge.in2p3.fr/dmsf/files/3811) (RD-7).
The files are named after its first extension (normally one per file or a
GROUP), followed by flag/code.

The coding depends on the frequency of update of the calibrations tables:
- Configuration tables can be updated every week.
- Ground calibration tables are changed when a new processing is needed,
   few times per year.

6.1. The ground calibration tables
In RD-7, the filename is the extension name followed by a flag with the
following structure:
  a) First digit is the main revision from 0 to 9: this is flag linked to a
  possible new processing and pipeline main revision:
    * A number with 1 digit from 0 to 9.
  b) x is a category letter (F,Q or T), depending whether it is:
    * Flight tables (F)
    * Qualification tables (Q)
    * ground Test tables (T)
  c) The last 2 digits is for subversion:
    * A number of 2 digits from 01 to 99).
For example the coding can be 1T01 (main revision 1, T=Ground Test table,
subversion 01).

6.2. The configuration tables
They can change every day (short time), (RD-7) preconizes to use the UTC day
with similar 3-field structure:
  a) yyyymmdd : yyyy for year, mm for month, dd for day,
  b) x for category letter (F,Q or T)
  c) Two last digit for consistency with calibrations table (and to ease
  T and Q versioning, less based on day)
For example the coding can be 20190718Q01 (yyymmdd=20190718, x= Qualification
table, version 01.)

6.3. Special case of uplinked tables
The tables are uplinked or downloaded with a version number (integer included
in the header bytes). The following naming has been proposed in RD-10, which
consists mainly in translating the string ground version into a unique 3 bytes
integer:
  - First 1 byte is for year and category:
    * 2 first bits are for category (0=Flight, 1=Qualification, 2=Test,
    3=spare value) [0 to 3]
    * Next, 6 bits is year starting from 2020 (so, it works until 2084, we
    have margin) [0 to 63]
  - Then 2 bytes for the Day Of the Year (DOY) and subversion:
    * First 4 bits is the month
    * Next 8 bits for day
    * Next 4 bits for subversion.
For example, for the date of December 5, 2020, if it is a test table, the name
will be 0x80C051 and if it is a qualification table 0x40C051.

6.4. Examples
For the table of gain/offset (Section), which is a configuration table, with
EXTENSION=AUX-ECL-PIX-CAL, the fits file name can be for tables used during
Qualification on 18th July 2019:
  - AUX-ECL-PIX-CAL-20190718Q01.fits for Qualification test #1
  - AUX-ECL-PIX-CAL-20190718Q02.fits for Qualification test #2
For the Misalignment matrix (Section), which is a ground calibration. Table,
with EXTENSION=AUX-ECL-LOC-MIS, a possible fits file name is:
  - AUX-ECL-LOC-MIS-2F05.fits
For the table of bounds in channel of energy strips, which is a configuration
table to be uploaded, with EXTENSION=AUX-ECL-BND-CAL, for test on December 5,
2020, the fits file suffix is 20201205T01 translates into ECL-BND-CAL-0x80C051
(and for the same date the qualification table suffix 20201205Q01 translates
into ECL-BND-CAL-0x40C051). This time the suffix of the name is given with the
OBJ_NAME keyword. Annex table 15 -File naming/versioning and CalDB keywords
  - gives more details on the naming of the EIC products.
==============================================================================
