Input Data Simulation

From Tauwiki

Jump to: navigation, search

Contents

[edit] Test Report: Complete Data

Created full telemetry for normal imaging, dark imaging, Lamp and synthetic data by inserting suitable values. 
The data was created separately and telemetry as a combined file. 

create_level0:
=============
The create_level0 module works for normal imaging, dark imaging and Lamp , but not for synthetic.  It 
complains  that the file is invalid. The reason may be the program is searching for multiple frames of 
events(in text file), but in synthetic data there can be only one extension. This is to be handled in 
create_level0.

Now this module accepts only one telemetry file at a time. This is fine rather  than entering numerous 
command  line arguments for telemetry files, as we will have various combinations of telemetry with and
without associated data. So I modified the telemetry simulation program. 

Ingest
======
Fine. It is splitting into each file for each observation. This is independent of type of imaging, but 
depends on  if log file is present or not. Do we need to handle the situation, where the log is missing ?.

Header of Files (create_level1a) :
================================
Filter values are not same in all extension headers of the same observation. For first few extensions 
it is 2 and  the remaining it is 0. Primary header it is 0. But both of these values are not what is 
given in telemetry which is  1. Need to test for more files, but this has to be checked in create_level1a.


Modules:
=======
The above is needed  because we need to check for them in modules  (register_data) in order to decide whether
 that module is applicable for the data. For example register_data is to be avoided for calibration data: 
Synthetic, Dark and Lamp, because  these events are created with closed filter. Any other steps needed 
to handle it ?

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. 

I think Dark imaging, Lamp and Synthetic belong to Calib. This is what I could  figure out from IRS document of
 Elop.  If so the value 4 for SYSMOD means 'skip the  register_data module'.

Now no difference in handling normal imaging, dark imaging, Lamp or synthetic data in any of modules.

Resources
=======
The data format tells  Lamp bits and log entries of commands, which are relevant for double checking to decide
 whether the data belongs to Calib or Normal Imaging.



The telemetry is created in java, now as command line arguments, but GUI is available as optional; 
need to enable fields and make parameter file an option. 

TODO
====
1. Write  all the relevant telemetry and log values in Wiki. 
2. Create log files by adding relevant command data. 
3. Simulate data for real dates. (Got file from Rita.)

In short
=====
1. create_level0 is not accepting Synthetic data frame (only one frame). 
2. Primary header should contain SYSMOD, which is already there in extension headers.
3. Check for the  SYSMOD value. If it is 4, that means Calibration and register_data need to be avoided.
4. Cross check header values with telemetry and log values across create_level0 and level1a modules. 
Filter entry is found changing in the same file (observation) itself. This is wrong.



[edit] Telemetry, Log and Time frame parameters

[edit] Imaging Modes

[edit] SRS (Section 3.2)

[edit] IMAGE Mode

In this mode, TAUVEX collects radiation, process it, store it and output the data to the transmitters.
The imaging types can be :
⇒ Normal imaging
⇒ Dark imaging (imaging while the filters before the detector are opaque)
⇒ Lamp imaging mainly for BIT purposes

[edit] CLBR (Calibration) Mode

In this mode, calibration process is carried out. The calibration process is a type of observation without the HVPSs turned on. Artificial events are sent to the input of the AFE cards. This is used to measure the DC offset of the W, S, and Z values coming out of the detectors' pre-amplifiers.


[edit] Static Telemetry Block

[edit] System mode

System mode       1 INIT mode     ; Values 1-A, 0x0D,  0x0F 
                  2 STBY mode
                  3 IMAGE mode
                  4 CLBR mode
                  5 BIT mode
                  6 OUTGAS mode
                  7 PRE-SHUT mode
                  9 PRE-CLBR submode
                  A POST-CLBR (sub-
                    mode)
                  D PRE-IMAGE (sub-
                    mode)
                  F POST-IMAGE
                    (submode)

[edit] Telescopes status

        Telescope#1       0/1      0 Lamp off
        lamp state                 1 Lamp on

        Telescope#2       0/1      0 Lamp off
        lamp state                 1 Lamp on

        Telescope#3       0/1      0 Lamp off
        lamp state                 1 Lamp on



[edit] Filter Status


Telescope#1  0-3 0 - BBF
filter state     1 - SF1
                 2 - SF2
                 3 - Close
Telescope#2  0-3 0 - Close
filter state     1 - SF1
                 2 - NBF3
                 3 - SF3
Telescope#3  0-3 0 - BBF
filter state     1 - Close
                 2 - SF2
                 3 - SF3





[edit] 3.2.1.2.1. Start Imaging Command (IRS)

Image type

           0 - Normal imaging
           1 - Dark imaging
           2 - Lamp imaging

CSS 2.1 Xhtml 1.0 Last Modified: February 22, 2007 GooglePagerank