This document guides one through two steps required to analyse raw RadMON output and calculate the dose in Gy, the HEH fluence in cm^-2 and the 1MeV NEQ fluence in cm^-2.
The scripts are self-sufficient provided that fundamental RadMON configurations are not changed.
Common sense of the positional context of the RadMON system (motherboard + deported module) for the run being analysed must be taken into account when considering the output of the scripts.
a. Sec 1 – File: excel -> Timescale in fixed intervals -> 10 sec SUM 1
b. RadMON variables -> Timescale in fixed intervals -> 10 sec AVG 2 (list below) This convention is important because:
-
Excel files can’t exceed 65’000 lines
-
The Matlab scripts rely on reading an excel file and the name of its sheets
This convention is practical because:
-
Facilitates matrix algebra, as every row will have the same date stamp
c. Separate RadMON data files by system and sensor:
-Dose script:
SEC 1 data file
RadMON version #, system # file (2 sheets): a. 400nm rfet in first sheet b. 100nm rfet in second sheet
- 1-MeV NEQ script:
SEC 1 data file
RadMON version #, system # file single sheet
-Risk Factor script (provides both HEHs and thNs):
SEC 1 data file
RadMON version #, system # file (2 sheets):
a. Cypress memory bank (B1)
b. Toshiba memory bank (B2)
If V5 – needs two motherboards to use (2 sheets)
a. Toshiba @ 5 volts on first sheet
b. Toshiba @ 3 volts on second sheet
a. Set up a convenient folder and filename system for output
The script needs both files to be in the same file directory
b. Change target input file names in the beginning of the script as appropriate
c. Set name of file location in the png, matlab figure and variable output lines
d. Run the script (F5)
a. The scripts are currently named so that they’re easy to identify but this is not supported by matlab (-> delete the %%%s )
b. The scripts need the extra functions in the root folder to work
c. New radfets/pin diodes = new initial voltages
This needs to be corrected in the initvoltages file (keep a copy of the old version and document the new change carefully!)
Or manually in the script
d. 90% of possible issues in the past were related to calculation errors involving matrixes of different sizes -> this should not be a problem now
e. V6 logs raw data in V, V5 logs it in mV
a. Run timings can be found (resource not in use).
b. Run setup can be looked at in the CHARM e-logbook
c. RadMON locations can be found (resource not in use).
1 SUM filtering is used on the SEC such that every event recorded is count and thus an accurate POT is retrieved.
2 AVG filtering is used on the data because it is integrated over time, SUM for example would produce incorrect data sets. A 10 second window is a good compromise in order to shorten the length of the data set whilst correctly capturing any discernible variability in the sensor signal over time. ( = it does not change drastically during 10 seconds)
Variable lists:
a. Radfets V5, PIN diodes V5, SEU counts V5:
RADMON.CHARM3:RAW_RF1
RADMOND.CHARM3:RAW_RF2
RADMOND.CHARM5:RAW_RF1
RADMOND.CHARM5:RAW_RF2
RADMOND.CHARM3:RAW_PIN3
RADMOND.CHARM5:RAW_PIN3
RADMON.CHARM3:SEU_COUNTS_INT
RADMON.CHARM5:SEU_COUNTS_INT
b. Radfets V6, PIN diodes V6, Bank1 counts V6 (Cypress, 3.3V), Bank 2 (Toshiba 3V)
SIMA.CHARMB3:RADFETS_0
SIMA.CHARMB3:RADFETS_1
SIMA.CHARMB4:RADFETS_0
SIMA.CHARMB4:RADFETS_1
SIMA.CHARMB5:RADFETS_0
SIMA.CHARMB5:RADFETS_1
SIMA.CHARMB6:RADFETS_0
SIMA.CHARMB6:RADFETS_1
SIMA.CHARMB7:RADFETS_0
SIMA.CHARMB7:RADFETS_1
SIMA.CHARMB8:RADFETS_0
SIMA.CHARMB8:RADFETS_1
SIMA.CHARMB3:PINDIODES_0
SIMA.CHARMB4:PINDIODES_0
SIMA.CHARMB5:PINDIODES_0
SIMA.CHARMB6:PINDIODES_0
SIMA.CHARMB7:PINDIODES_0
SIMA.CHARMB8:PINDIODES_0
SIMA.CHARMB3:SEU_B1_COUNTS_INT
SIMA.CHARMB3:SEU_B2_COUNTS_INT
SIMA.CHARMB4:SEU_B1_COUNTS_INT
SIMA.CHARMB4:SEU_B2_COUNTS_INT
SIMA.CHARMB5:SEU_B1_COUNTS_INT
SIMA.CHARMB5:SEU_B2_COUNTS_INT
SIMA.CHARMB6:SEU_B1_COUNTS_INT
SIMA.CHARMB6:SEU_B2_COUNTS_INT
SIMA.CHARMB7:SEU_B1_COUNTS_INT
SIMA.CHARMB7:SEU_B2_COUNTS_INT
SIMA.CHARMB8:SEU_B1_COUNTS_INT
SIMA.CHARMB8:SEU_B2_COUNTS_INT