Test Results of Modules
From Tauwiki
Contents |
[edit] create_level0
This module accepts combined telemetry file, while data and log files can be separate. The create_level0 module works for events text input files for normal imaging, dark imaging and Lamp.
[edit] Synthetic data
Synthetic data can have only one extension. This is because there is no time frame transmitted between the events. But this doesn't mean that the synthetic data is limited to 128 ms. The telemetry file created contains as many frames (128 ms interval) as needed to fill the transmission duration of synthetic data.
The synthetic data events from the input text file have to be converted to data format and the corresponding telemetry frames have to be added with it. The corresponding frames of telemetry can be selected by comparing the key words.
The Telescope Status contains one byte data. The 7th bit starting from lsb indicates whether it is 'Synthetic' or 'Normal Image' if it is 1 or 0.
#byte 8 TELESCOPE_STATUS
This can be combined with the
#byte 5 SYSTEM_MODE
If this is 3, it is Normal Imaging; if it is 4, then Calibration.
After finishing writing the Synthetic data, the values of the above bytes need to be checked and frames till the 'Synthetic ' imaging bit is true, are to be taken together. This grouping is important in the new data format (to be modified).
Do Dark imaging, Lamp and Synthetic belong to Calibration ?
Will we get GSAT telemetry information when Tauvex is off, or when data is missing ?.
[edit] Test Report
The files are attached in mailing list mail as files.tar.gz
1st file: -------- In leve1a file <20-20.1-20.2-20.3-N-D_0__T1_1a.fits> In frame 0: RA_START = 20.0 In Frame_no = 173: RA_CENT = 20.09168 Total frames in the file = 174. In file : <20-20.1--77-normal.txt> $ 00173 RA = 20.092801 DEC = -77.000000 (in degrees) And last frame is : $ 00187 RA = 20.100267 DEC = -77.000000 (in degrees) So 187 -173 = 14 frames missing in level1a. =========================================== Second file: ----------- In file: <20-20.1-20.2-20.3-N-D_1_T1_1a.fits> In frame 0: RA_START = 20.10213 In frame 1: RA_START = 20.10053 In Frame_no = 186: RA_CENT = 20.19914 Total frames in the file = 187(endlog) In <20.1-20.2--77-Dark10.txt> In frame 1: RA_START = 20.10053 $ 00186 RA = 20.199734 DEC = -77.000000 (in degrees) $ 00187 RA = 20.200267 DEC = -77.000000 (in degrees) The last frame is missing in level1a fits file. ============================================ Third file: ----------- <20-20.1-20.2-20.3-N-D_2_T1_1a.fits> In frame 0: RA_START =20.20107 In Frame_no = 188: RA_CENT = 20.30074 In <20.2-20.3--77-dk5K-Lamp.txt> $ 00000 RA = 20.200533 $ 00187 RA = 20.300267 DEC = -77.000000 (in degrees)
[edit] Separate Events for Each Telescope
Ideally the synthetic data event file should be different for each Telescope. 1. I will create separate set of events for each Telescope in the same text file itself separated by suitable # keyword. 2. It would be nice if these events are distributed among the Telescopes in create_level0. This may be useful in the testing phase of the MCF setup, if they want the simulated data from us.
[edit] Ingest_data
This is working as required. It is splitting the input into separate file for each observation. This is independent of type of imaging, but depends on if log file is present or not. (Ideally, if the log is missing, the telemetry values and observation mode can be compared with the same from previous frame to see if the file is by the same observation or not.)
[edit] Combine_level1a
Not Tested.
The conclusion of the discussion of its working: <.br> If the data is missing for more than defined duration, then it has to be marked as incomplete data. Now log part is attached with these parts which is not needed.
[edit] Create_level1a
1. Time mismatch :
The OBT and data time may differ in real case, when both counters start differently. This issue has to be handled. One has to feed the difference in these counters in to the module through parameter file entry, since this difference is same till the next reset of clocks.
2. The fits header entries need to be verified.
Primary Header of Fits Files
Filter values are not same in all extension headers of the same observation file. This has to be checked in create_level1a.
[edit] Register_data
Now no difference in handling normal imaging, dark imaging, Lamp or synthetic data in any of modules.
This module is to be avoided from running Synthetic, Dark and Lamp data. These can be done by checking system mode, 'SYSMOD' in primary header. That entry is missing now in primary header, but it is there in extension header. The value is 3 for normal imaging and 4 for Calibration. The value 4 for SYSMOD means 'skip the register_data module'.
