|
Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://xmm.vilspa.esa.es/calibration/documentation/CALHB/node653.html
Дата изменения: Tue Sep 20 19:45:20 2011 Дата индексирования: Mon Apr 11 03:15:50 2016 Кодировка: Поисковые слова: active galaxy |
This section contains descriptions of the structure of CCF constituents. These descriptions will however only be to the extent that all items that are relevant for the instrumental calibrations will be listed. Overall keywords that are required for the proper archiving and management of the CCF will be omitted, as they are to be detailed in [5].
The coordinates used inside the CCF files will be consistent with the coordinate conventions as is used by the SAS (see CAL documentation for a description). Consequently all coordinates specified in terms of RAWX & RAWY start at 1, which depending on the instrument, may be different than in telemetry.
The calibration team of the SOC is also providing additional CCF components where required in conjunction with data that were generated with SciSim. This is only a temporary solution in order to get calibrated test data on a short time scale for testing SAS task. The goal for the long run is to update SciSim such that it produces data similar to the instruments' performances, and thus eventually no special CCF components will be needed.
These CCF components are generated on a need basis and are identical in structure to the real life components. The difference between the instances of a real life CCF component and its SciSim applicable counterpart is that the CATEGORY keyword either is set to XMMCCF, or to SCISIMCCF, respectively.
As far as the CAL is concerned there is only one CCF, i.e., the one the user points at with the SAS_CCFDIR environment variable. The calibration index file (CIF) in that directory will tell the CAL how to find the various constituents it needs. However, this flexibility can be used at the CIF-building stage. The task cifbuild can locate CCF constituents along a specified search path (see cifbuild description, GV note). So, assuming the constituents of scisimccf/xmmccf are located in different directories the former does not need to contain the entire set if the latter does. In other words, scisimccf does only need to contain the scisim-specific parts (which cifbuild will pick if scisimccf comes BEFORE xmmccf in the CCF search path).