-
Notifications
You must be signed in to change notification settings - Fork 18
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
rename and move data maniplation functions #237
Comments
See #217 for ideas |
My current idea is to make them "first level citizens" (not sure if this is the correct term), i.e.: mesmer.grid
mesmer.mask
mesmer.weighted
mesmer.grid.wrap_to_180(...)
mesmer.mask.mask_ocean(...)
mesmer.weighted.global_mean(...) where I would move the .py files to core and then import from there. I don't like to have them two levels down ( |
Happy to reconsider if there is a better idea... |
After #274 I renamed this issue as I am not yet sure that the names are final (i.e. if I am totally happy with them). This concerns: mesmer.mask.mask_ocean_fraction
mesmer.mask.mask_ocean
mesmer.mask.mask_antarctica
mesmer.globmean.lat_weights
mesmer.globmean.weighted_mean
mesmer.core.computation.calc_geodist_exact
mesmer.core.computation.gaspari_cohn
I am happy with
|
|
closing in favor of #348 |
edited the title after #274. The old title was rename the xarray_utils?
It's a bit a generic, bland name and does not say much. Also @jschwaab prefered something else. Worth reconsidering before v0.9.0
The text was updated successfully, but these errors were encountered: