-
Notifications
You must be signed in to change notification settings - Fork 41
Idex release two updates #3399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Idex release two updates #3399
Changes from all commits
2f10bf8
3a2b3af
e761beb
204e3c9
76a4275
fec1ed1
118d907
69b9c08
1c80d14
8566c76
0f16d72
74db977
c433242
6674c4c
06cc24d
eeff14b
0165f7f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -48,6 +48,16 @@ trigger_base: &trigger_base | |
| DISPLAY_TYPE: no_plot | ||
| UNITS: " " | ||
|
|
||
| event_flag_base: &event_flag_base | ||
| <<: *trigger_base | ||
| CATDESC: "Boolean event classification flag." | ||
| CDF_DATA_TYPE: CDF_UINT1 | ||
| FILLVAL: 255 | ||
| FORMAT: I1 | ||
| UNITS: " " | ||
| VALIDMAX: 1 | ||
| VALIDMIN: 0 | ||
|
|
||
| spice_base: &spice_base | ||
| <<: *l1b_data_base | ||
| DISPLAY_TYPE: time_series | ||
|
|
@@ -57,6 +67,66 @@ spice_base: &spice_base | |
| VAR_TYPE: data | ||
|
|
||
| # <=== Instrument Setting Attributes ===> | ||
| science_event_flag: | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Have you validated that these new attrs are ISTP compliant?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Alex is going to use SKTeditor to check
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Best I can tell, these values are compliant. The webpage checker doesn't seem to like a fill-value of 255 but it's what we use across other variables so I think we leave it as is.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What was the error? Can you attach a screen shot? 255 may be a valid fill val for other variables but not these if its not configured properly.
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ISTP checker now returning compliance for the flags! Thanks for catching those issues.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. excellent. Super appreciate you checking. |
||
| <<: *event_flag_base | ||
| CATDESC: Science event classification flag. | ||
| FIELDNAM: Science Event Flag | ||
| LABLAXIS: Science Event | ||
|
|
||
| noise_capture_flag: | ||
| <<: *event_flag_base | ||
| CATDESC: Noise capture event classification flag. | ||
| FIELDNAM: Noise Capture Flag | ||
| LABLAXIS: Noise Capture | ||
|
|
||
| pulser_flag: | ||
| <<: *event_flag_base | ||
| CATDESC: Pulser event classification flag. | ||
| FIELDNAM: Pulser Flag | ||
| LABLAXIS: Pulser | ||
|
|
||
| dust_hit_flag: | ||
| <<: *event_flag_base | ||
| CATDESC: Dust Hit waveform classification flag. | ||
| FIELDNAM: Dust Hit Flag | ||
| LABLAXIS: Dust Hit | ||
|
|
||
| tof_high_saturation_flag: | ||
| <<: *event_flag_base | ||
| CATDESC: TOF High waveform saturation flag. | ||
| FIELDNAM: TOF High Saturation Flag | ||
| LABLAXIS: TOF HG Saturation | ||
|
|
||
| tof_mid_saturation_flag: | ||
| <<: *event_flag_base | ||
| CATDESC: TOF Mid waveform saturation flag. | ||
| FIELDNAM: TOF Mid Saturation Flag | ||
| LABLAXIS: TOF MG Saturation | ||
|
|
||
| tof_low_saturation_flag: | ||
| <<: *event_flag_base | ||
| CATDESC: TOF Low waveform saturation flag. | ||
| FIELDNAM: TOF Low Saturation Flag | ||
| LABLAXIS: TOF LG Saturation | ||
|
|
||
| target_high_saturation_flag: | ||
| <<: *event_flag_base | ||
| CATDESC: Target High waveform saturation flag. | ||
| FIELDNAM: Target High Saturation Flag | ||
| LABLAXIS: Target HG Saturation | ||
|
|
||
| target_low_saturation_flag: | ||
| <<: *event_flag_base | ||
| CATDESC: Target Low waveform saturation flag. | ||
| FIELDNAM: Target Low Saturation Flag | ||
| LABLAXIS: Target LG Saturation | ||
|
|
||
| ion_grid_saturation_flag: | ||
| <<: *event_flag_base | ||
| CATDESC: Ion Grid waveform saturation flag. | ||
| FIELDNAM: Ion Grid Saturation Flag | ||
| LABLAXIS: Ion Grid Saturation | ||
|
|
||
| trigger_mode_lg: | ||
| <<: *string_base | ||
| CATDESC: Low Gain Trigger Mode. | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I see. There are a couple of issues here.
I would not use "trigger_base" as the base because those are for variables that are not quality flags. So I would remove that part.
Second, make sure the array is actually np.unit8 e.g. data.astype(np.uint8)
It thinks the data is np.uint64 as implied by the warning.