Description of the issue
When creating L2 data, using imap_processing locally, applying an l2-offsets file with matching timestamps to a partial day of L1C normal mode data creates an L2 files with FILLVAL values in it. No NaNs or FILLVALs are present in the L1C data or in the l2-offsets data.
Steps to reproduce the issue
- Use a partial day of MAG data, where data is missing (eg April 30th)
- Using L1C norm data from that day with no NaNs/FILLVALS, and a matching l2-offsets file from the MAG team with no NaNs/FILLVALS, run L2 processing
- Resulting file has NaNs/FILLVALS
Expected vs Actual behavior
The resulting L2 file should be incomplete (as with the L1C file), but it should not have any NaNs/FILLVALS when there are none present in either the original data, or in the offsets file
Code Snippet (If applicable)
Additional notes, affected areas, and suggested fixes
No response
Description of the issue
When creating L2 data, using
imap_processinglocally, applying anl2-offsetsfile with matching timestamps to a partial day of L1C normal mode data creates an L2 files with FILLVAL values in it. No NaNs or FILLVALs are present in the L1C data or in the l2-offsets data.Steps to reproduce the issue
Expected vs Actual behavior
The resulting L2 file should be incomplete (as with the L1C file), but it should not have any NaNs/FILLVALS when there are none present in either the original data, or in the offsets file
Code Snippet (If applicable)
CodeAdditional notes, affected areas, and suggested fixes
No response