-
Notifications
You must be signed in to change notification settings - Fork 7
BUG - SWAPI L3a proton-sw ISTP compliance #102
Copy link
Copy link
Open
Labels
Data Release 1Deadline: June 15, 2026Deadline: June 15, 2026Ins: SWAPIRelated to the SWAPI instrumentRelated to the SWAPI instrumentRelease BlockerNeeds to be addressed before (next) public releaseNeeds to be addressed before (next) public releasebugSomething isn't workingSomething isn't working
Metadata
Metadata
Assignees
Labels
Data Release 1Deadline: June 15, 2026Deadline: June 15, 2026Ins: SWAPIRelated to the SWAPI instrumentRelated to the SWAPI instrumentRelease BlockerNeeds to be addressed before (next) public releaseNeeds to be addressed before (next) public releasebugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for Bug.
Projects
Status
Todo
Description of the issue
Looking at imap_swapi_l3a_proton-sw_20260421_v021.cdf, there are several ISTP compliance failures with the work from #99
proton_sw_bulk_velocity_rtn_scandproton_sw_bulk_velocity_rtn_sunhave aDEPEND_1ofrtn_label.rtn_labeldoesn't exist. The label should beLABL_PTR_1andrtn_labelshould be a CDF_CHAR variable withVr,Vt,Vnor similar. NoDEPEND_1is needed for simple axes anymore; see ISTP standard examplesproton_sw_bulk_velocity_rtn_sc_covarianceandproton_sw_bulk_velocity_rtn_sun_covarianceneedLABL_PTRfor both dimensions.proton_sw_bulk_velocity_rtn_sc_covarianceandproton_sw_bulk_velocity_rtn_sun_covariancehave a lot of values under 0 and aVALIDMINof 0; presumably theVALIDMINneeds to be updatedkm/sSteps to reproduce the issue
No response
Expected vs Actual behavior
No response
Code Snippet (If applicable)
CodeAdditional notes, affected areas, and suggested fixes
No response