-
Notifications
You must be signed in to change notification settings - Fork 26
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
Further plot updates and fix observed contour lines #185
Conversation
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.
Let me know if you still want to make additional changes or if this is ready?
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.
Besides the comment about the directory structure of the obs datasets, I'm a little confused about how path_nsidc
is defined inside plot_diff.py
. Can this be an argument passed in from the notebook, so this function works on computers that don't have access to campaign store? A couple of related questions:
- is
path_nsidc
the right variable name? (Is this still NSIDC data? Isn'tHadOIBl
coming from UKMO?) - Should we have something like
obs_data_root
that is set to/glade/campaign/cesm/development/cross-wg/diagnostic_framework/CUPiD_obs_data/ice/analysis_datasets
inconfig.yml
and then we build up all the otherpath_
variables from that?path_nsidc = os.path.join(obs_data_root, 'hemispheric_data', 'NSIDC_SeaIce_extent')
,path_hadoibl = os.path.join(obs_data_root, '1x1', 'HadOIBl')
, etc?
This might require a little clean up in the other ice notebooks and .py
files, but it will set a good precedent for later updates
Ok. I have merged Alice's changes and I think this is ready for review. |
Whoops. I missed that. I think we might have some conflicts. Can you remove these from your PR to keep it separated? |
We'll still need the first part of the parameters (eg, parameter = "" #comment instead of #parameter="")-- thus, I think your changes listed here will not actually work with the parameters cell. Also, this is really more related to the observational repository changes than to this PR, so I'd prefer to leave it in #191. I'll remove the changes here though. |
I think merging the latest |
That's exactly what I just did :) |
I think this is ready. I have fixed the parameter boxes and now use obs_data_dir. |
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.
I focused on the Hemis_seaice_visual_compare_obs_lens.ipynb
notebook, because that's what gets run in key_metrics
, and didn't look closely at Hemis_seaice_visual_compare_contour.ipynb
. I have a few minor comments about the obs_lens
notebook:
path_model
is inconfig.yml
but not in the default parameter cellobs_data_dir
is used in the definition ofpath_nsidc
but also appears in calls likeos.path.join(obs_data_dir, path_nsidc, "N_01_extent_v3.0.csv")
; I think you just wantpath_nsidc = os.path.join("ice", "analysis_datasets", "hemispheric_data", "NSIDC_SeaIce_extent")
(formatted howeverpre-commit
decides it should be formatted)
Also, I'll fix this in a separate PR but currently these notebooks don't support CESM_output_dir
and base_case_output_dir
being different
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.
Thanks for making these changes, this looks like it is ready to merge!
Description of changes:
All PRs Checklist:
pre-commit
checks passed (#8 in Adding Notebooks Guide)?New notebook PR Additional Checklist (if these do not apply, feel free to remove this section):
parameters
? These can cause confusing warnings that show up asDAG build with warnings
./glade/campaign/cesm/development/cross-wg/diagnostic_framework/CUPiD_obs_data
and ensured that it follows this format within that directory:COMPONENT/analysis_datasets/RESOLUTION/PROCESSED_FIELD_TYPE
?