-
Notifications
You must be signed in to change notification settings - Fork 6
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
GUVI imaging updates #198
GUVI imaging updates #198
Conversation
Fixed the JHU APL load routines to handle an empty file list.
Updated labels definition to use meta labels attributes instead of strings and keys.
Updated the TIMED GUVI clean method for imaging data.
Fixed the dictionary formatting for `_clean_warn`.
Allow for channels when masking for the clean routine.
Removed extra whitespace and some typo characters in the docstring.
Added a concat_data method to fix issues loading data.
Remove the time sorting in `concat_data`, as data should be concatenated in the desired order.
Updated the changelog with a summary of the changes in this branch.
Added a whitespace after the `if` keyword. Also replaced hardcoded key with the appropriate variable.
Added metadata for the 'time_auroral' and 'nCross' variables.
What's the status of this pull? Is it waiting on a new pysat release? |
Yes, it requires a pysat release. |
Testing this branch against the pysat 3.2.0 RC, I see the following failures (for guvi):
Full error output at https://github.com/pysat/pysatNASA/actions/runs/7051616139/job/19194923688 |
Pull Develop changes into guvi branch
@aburrell, I think to finish this one we just need to fix the |
Fix time where microseconds can become too big from rounding.
Updated type equalities to use `isinstance`.
Added a `linkcheck_ignore` statement, as the GATS page checks to see if the link request is human or machine.
Ensured that only dimensions with data are renamed. Also updated test date to highlight a time with better data coverage across all instruments.
@jklenzing I fixed both GUVI errors. The first one was a data-availability issue. I picked test days with better coverage and everything looks good. |
Update TIMED GUVI test dates, as coverage needs are different for different instruments.
TODO:
|
Running vs the RC, there is a segmentation fault in the ubuntu branch: https://github.com/pysat/pysatNASA/actions/runs/8163504069 Reran the branch, happened again. The develop branch passes without issue. |
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.
Verified that the new lines of code are being run when using pysat 3.2.0rc6 (which accounts for the drop in coverage in this PR). Not sure why the segmentation fault appears in ubuntu but not the other ones.
Fixed the segmentation fault issue. Applying the skip test flags to the high-res data only allows the new concat routines to be tested, while avoiding memory issues on GA. https://github.com/pysat/pysatNASA/actions/runs/8189899989 |
From the tests:
|
Description
Addresses #197 by adding a custom
concat_data
method to the TIMED GUVI instrument. This requires the pysat pull request: pysat/pysat#1131 to work.Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Load TIMED GUVI data for the
sdr-imaging
tag. Check and see that the Auroral data does not have the 'time' dimension, rather it has only the 'time_auroral' dimension (in addition to other appropriate dimensions). Also, the extent of the 'time_auroral' dimension should be limited to the period of time encompassed by 'time'.Yields:
Also, there should be no warnings raised when loading the data, as there is meta data for all variables and cleaning applied to these data tags/inst IDs.
Finally, unit tests should be run locally against pysat/pysat#1131 to ensure appropriate behaviour with updated pysat handling.
Test Configuration:
inst_concat_data_method
Checklist:
develop
(notmain
) branchCHANGELOG.md
, summarizing the changesIf this is a release PR, replace the first item of the above checklist with the release
checklist on the wiki: https://github.com/pysat/pysat/wiki/Checklist-for-Release