Instructions & Details on how to use the EAS In-Flight Calibration

 

1. The EAS Calibration Pipeline works on data that is stored in:

    /disk/swa01/Software/SWA_TM_TC_data/CCSDS_binary/

    This is binary data with a .binary extension

 

2. The pipeline codes are kept in /disk/swa01/Software/EAS_InFlight_Calibration/

 

3. The Extractor code is called EAS_CalibData_Extractor

 

4. If you make changes to the .cpp then re-compile it with:

g++ EAS_CalibData_Extractor.cpp -o EAS_CalibData_Extractor.bin

 

5. To run the code, go to /disk/swa01/Software/EAS_InFlight_Calibration/ and use this:

./EAS_CalibData_Extractor.bin [Input File].binary [Output].csv

 

6. The Output file name can be anything but I have been using this format:

yyyymmdd.csv

 

7. The saved .csv file are text files and can be used and viewed but will probably only be used by the next part of the pipeline.

 

8. The .csv files are saved in

/disk/swa01/DocumentRoot/Data/SWA/EAS_InFlight_Calibration/CSV/

 

9. The EAS_CalibData_Extractor will take the daily binary data file and extract all the EAS calibration test data, EM3 and EM4. It will save it out into a .csv file. Both EASs are included in this file.

 

10. The contents of the .csv are

epoch - date and time

Type - always 21

Subtype -  always 3

SID – EAS1=18, EAS2=48

SID counter – an incrementing packet counter

scet1 – The sc ephemeris time

scet2

scet3

mode1 – Details of the MCP voltage or the threshold setting

mode2

mode3

Spare

Spare

32 anode values

 

11. Having made the .csv file. This is then fed into EAS_GainTest_Pipeline.pro and/or EAS_ThreshTest_Pipeline.pro

 

12. The output of the EAS_GainTest_Pipeline.pro is an IDL .dat save file.

 

13. The files are called ÔGainTest_yyyymmddThhmmss_[EAS type]_[fixed or sweep].dat

 

14. The file contents are:

EPOCH           STRING    = yyyymmdd

EAS_TIME        STRING    = Array[n]

EAS_DECTIME     FLOAT     = Array[n]

EAS_MCP         FLOAT     = Array[n]

EAS_COUNTS      DOUBLE    = Array[n, 32]

 

15. The output of the EAS_ThreshTest_Pipeline.pro is an IDL .dat save file.

 

16. The files are called ÔThresholdTest_yyyymmddThhmmss_[EAS type].dat

 

17. The file contents are:

EAS_EPOCH              STRING    = 'yyyymmddThhmmss'

SENSOR                 STRING    = 'EAS1' or ÔEAS2Õ

EAS_TIME_SWEEP1        STRING    = Array[m]

EAS_TIME_SWEEP2        STRING    = Array[n]

EAS_DECTIME_SWEEP1     FLOAT     = Array[m]

EAS_DECTIME_SWEEP2     FLOAT     = Array[n]

EAS_THRESH_SWEEP1      FLOAT     = Array[m]

EAS_THRESH_SWEEP2      FLOAT     = Array[n]

EAS_COUNTS_SWEEP1      DOUBLE    = Array[m, 32]

EAS_COUNTS_SWEEP2      DOUBLE    = Array[n, 32]

 

18. The sweep 1 & 2 refer to the preamp sweeps.

The EAS_Thresh is the threshold applied to the DAC.

The m & n are governed by how many steps are in the test and where in the EAS cycle the test is started.

 

19. The Threshold test files and the Gain test files are saved in:

/disk/swa01/DocumentRoot/Data/SWA/EAS_InFlight_Calibration/Results/