Skip to content
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

Absorb fre-workflows/app/remap-pp-components --> fre pp remap... or fre cmor <subtool> ? #134

Closed
ilaflott opened this issue Jul 29, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@ilaflott
Copy link
Member

Is your feature request related to a problem? Please describe.
we wish to have proper fre-cli access to remap-pp-components routines used within the python/FRE2 ecosystem. Currently, remap-pp-components is a routine within fre-workflows.

Describe the solution you'd like
this is less trivial than the other two tool-absorption issues, due to significant overlap with fre/cmor/CMORmixer.py

Describe alternatives you've considered

Additional context
a lot of this has to do with making sure directory structure for postprocessing output is in a format that fre-bronx understood. This directory structure is important for producing CMIP-publishable model output.

This issue should probably have it's description and desired solution updated as more information becomes available.

@ilaflott ilaflott added the enhancement New feature or request label Jul 29, 2024
@ilaflott
Copy link
Member Author

After more thought, really this should be worded like, "have fre-workflows/app/remap-pp-components call fre cmor".

Which also means this issue belongs in fre-workflows and development effort belongs there. thoughts?

@Ciheim
Copy link
Collaborator

Ciheim commented Oct 31, 2024

Definitely seems more appropriate for the issue to be there @ilaflott

@ilaflott
Copy link
Member Author

this will be addressed in fre-workflows here: NOAA-GFDL/fre-workflows#38

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants