Double Star PEACE Prime Parameters
Latest Version : 5.0
Information in the data files:
interval centred
(click here for more information)
Status[0]
Data quality as defined by CSDS
value
|
interpretation
|
0
|
bad data
|
1
|
use with caution
|
2
|
OK
|
255
|
fill value
|
Status[1] Moments Calculation Route
value
|
interpretation
|
0
|
data removed
|
1
|
produced from transmitted 2D
velocity distribution |
2
|
produced from transmitted 3D
velocity distribution
|
3
|
produced from transmitted JPEG
compressed 3D
velocity distribution
|
Status[2] Moments Production Key
bit
|
value
|
interpretation
|
7
|
0
|
on two consecutive spins the
sensor covers the same energy range
|
|
1
|
on two consecutive spins the
sensor covers different energy ranges
|
6
|
0
|
full energy range of high energy
spins transmitted
|
|
1
|
overlap region of high energy
spins not transmitted
|
5
|
0
|
low energy spin
|
5
|
1
|
high energy spin
|
4
|
-
|
not used
|
3
|
0
|
spacecraft potential determined
using PEACE onboard software |
|
1
|
spacecraft potential determined
on ground |
2
|
1
|
ASPOC on
|
1
|
1
|
QM corrector used |
0
|
0
|
lowest measured energy > V_SC
|
|
1
|
lowest measured energy < V_SC |
Status[3] Supporting Information
bit
|
value
|
interpretation
|
7
|
1
|
caution : risk of low statistics
|
6
|
1
|
caution : risk of saturation
|
5
|
-
|
not used
|
4
|
-
|
not used
|
3
|
1
|
PEACE sensor to DPU data
transfer error
|
2
|
1
|
no FGM data available
|
1
|
-
|
not used
|
0
|
-
|
not used
|
electron density in cm-3
electron GSE velocity in km/s
parallel electron temperature in MK
perpendicular electron temperature in MK
parallel electron heat flux in mu J m-2
s-1
Notes
Removal of data
Data is removed under the following conditions:
- during MCP tests. MCP tests are detected by checking that HAR
mode is used, and that the MCP levels are varying.
- when the MCP level is set to zero.
- the first 3 spins after a PEACE instrument is switched on.
Possible INST_MODE messages
Tn>PEA>m>YYYY-MM-DDTHH:MM:SS.SSSZ>PEA_On>88m28-60m00-f-aa
Tn>PEA>m>YYYY-MM-DDTHH:MM:SS.SSSZ>PEA_Eng>MCP_Test
88h58
Tn>PEA>m>YYYY-MM-DDTHH:MM:SS.SSSZ>PEA_Eng>Grid_On
Tn>PEA>m>YYYY-MM-DDTHH:MM:SS.SSSZ>PEA_Eng>Grid_Off
Tn>PEA>m>YYYY-MM-DDTHH:MM:SS.SSSZ>PEA_Off>PEACE_science_off
where n is the spacecraft number, and m is the record number that the
message first applies to.
Possible INST_SETTINGS messages
YYYY-MM-DDTHH:MM:SS.SSSZ>sunpulse rephase offset>1104
Versions
Important Note: the version number is given in the caveats. Do not use the
version number of the cdf file.
- crude S/C potential correction
- v1 calibration file
- crude S/C potential correction
- timing corrected
- v1 calibration file
- crude S/C potential correction
- additional timing corrections
- more detailed INST_MODE
messages
- v2 calibration file
- crude S/C potential correction
- further timing corrections
- more detailed INST_MODE messages (aa or ab listed)
- more detailed status bytes
- calibration version information included (Calib_input)
- reference to the Double Star instrument paper included
- v1 calibration file used for TC-1 & TC-2
- additional caveats
- TC-2 2004-08-26 to 2004-08-31 contain fill values only due to
sweep preset problems with the IDFS data
- TC-2 2004-12-31 contains fill values only due to IDFS data
problems
- version 4.1
- same as version 4, but used PEACE science data from v2.0 raw -> IDFS ingestion
software (low & high energy red stripe removal included)
- same as version 4, but used PEACE science data from v2.1 raw
-> IDFS ingestion software (new Double Star IDFS 3DF data put into
the MSSL IDFS archive on 2005-11-01). The latest 3DF data has some fill
value problems corrected, and better red stripe removal.
- fill values in cdf files are correct
- note that when eclipse mode is used: (1) PP timestamps maybe incorrect, (2) PEACE moments may not be accurate. This will be improved in a future release of the Double Star PEACE Prime Parameters.
- same as version 4.2, but moments generated with improved inter-anode calibration
Last
Update: 09 Aug 2007, A.D. Lahiff