You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SPDF has requested that any simple 3D vectors or triangular (6 element) tensors have a LABL_PTR_1 that can be interpreted without reference to the LABLAXIS. That means both putting more information into the values of the variable pointed to by LABL_PTR_1 and splitting those variables, so that basically every data variable has its own label variable. Detailed list in "requirements" below
Things that do not have to change:
Only applies to data variables, so we'll not bother on support_data
Unless noted otherwise, the existing label pointer variable should stay, as it will be used for higher-dimensionality quantities (covariances) and support_data variables (e.g. uncertainties)
Similarly, the LABLAXIS should stay, as there are utilities that use it.
If there is a DEPEND pointing to a simple 1, 2, 3 or similar numeric, it does not have to change...just the labels
We probably want to merge #128 before starting on this, as otherwise there are likely to be conflicts. I'm going to give SPDF a little bit of time to review those changes and then merge it myself.
Requirements
For each product and variable, this lists what the new labels should be; i.e. copy the metadata for the existing label, update as necessary (inheritance may be good here), and populate the NRV values in the code
For these three temperature tensor variables, change VAR_NOTES: "Calculated by integration over the measured phase space distribution. In despun pointing set (DPS) coordinates."
Remove temperature_tensor_label, but okay to use it as the basis for the above (e.g. inherit)
tensor_id can remain as-is (also leave references to it as-is)
Summary
SPDF has requested that any simple 3D vectors or triangular (6 element) tensors have a LABL_PTR_1 that can be interpreted without reference to the LABLAXIS. That means both putting more information into the values of the variable pointed to by LABL_PTR_1 and splitting those variables, so that basically every data variable has its own label variable. Detailed list in "requirements" below
Things that do not have to change:
We probably want to merge #128 before starting on this, as otherwise there are likely to be conflicts. I'm going to give SPDF a little bit of time to review those changes and then merge it myself.
Requirements
For each product and variable, this lists what the new labels should be; i.e. copy the metadata for the existing label, update as necessary (inheritance may be good here), and populate the NRV values in the code
['Va SC R', 'Va SC T', 'Va SC N']['Va Sun R', 'Va Sun T', 'Va Sun N']['Vp SC R', 'Vp SC T', 'Vp SC N']['Vp Sun R', 'Vp Sun T', 'Vp Sun N']['Core v fit R', 'Core v fit T', 'Core v fit N']['Halo v fit R', 'Halo v fit T', 'Halo v fit N']['Core v int. R', 'Core v int. T', 'Core v int. N']['Halo v int. R', 'Halo v int. T', 'Halo v int. N']['Total v int. R', 'Total v int. T', 'Total v int. N']['Core T_XX', 'Core T_XY', 'Core T_YY', 'Core T_XZ', 'Core T_YZ', 'Core T_ZZ']['Halo T_XX', 'Halo T_XY', 'Halo T_YY', 'Halo T_XZ', 'Halo T_YZ', 'Halo T_ZZ']['Total T_XX', 'Total T_XY', 'Total T_YY', 'Total T_XZ', 'Total T_YZ', 'Total T_ZZ']Related tickets
No response