-
Notifications
You must be signed in to change notification settings - Fork 11
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
606 circulation and fluxes in global model data #607
606 circulation and fluxes in global model data #607
Conversation
… wrap Code to co-locate velocities on T-points and do a nice surface plot
@jasontempestholt I'm still going through this. I made some changes in a new branch they broke the unit_testing! So it is not ready yet. |
…obal-model-data_jp' into 606-circulation-and-fluxes-in-global-model-data_jp # Conflicts: # coast/diagnostics/circulation.py # unit_testing/test_diagnostic_methods.py
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've taken your branch and:
- changed a few names to make them more COAsT
- abstracted and simplified your subsetting method in Gridded()
- refactored the velocity_on_t_points so that the differences across indices are not a function of dimension ordering (I'm also hoping it might scale better with xarray backend magic)
- updated to the latest version of Develop
- Unit testing still works.
One way to do this, so that it is still your branch, is if I request a merge into your branch. Then I will be ready to accept your branch.
NB there are a few name changes, which will affect your scripts (capitalisation mostly). These are the main (only?) two:
nemo_t = coast.CurrentsOnT(fn_domain=files.fn_nemo_dom, config=files.fn_config_t_grid, lims=lims)
nemo_t.currents_on_t(nemo_u, nemo_v)
…rculation-and-fluxes-in-global-model-data_jp 606 circulation and fluxes in global model data jp
Pull request checklist
Please check if your PR fulfills the following requirements:
COAsT-site
repo, in a separate PR. See contributing to documentation for details../build.sh
) was run locally and no errors reported. NB not sure about this requirement: GitActions test thispylint .
) has passed locally and any fixes were made for failures. NB not sure about this requirement: GitActions test this withblack
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Issue URL: #
What is the new behavior?
Checklist
pip install . && pytest unit_testing/unit_test.py -s
)Does this introduce a breaking change?
Other information
Quick update to add useful feature of subsetting for global models
and also some circulation calculations / plot, which will be further developed