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

should we change runtime commands "analysis_*" to "bgcval2_*"? #18

Open
ledm opened this issue May 6, 2022 · 2 comments
Open

should we change runtime commands "analysis_*" to "bgcval2_*"? #18

ledm opened this issue May 6, 2022 · 2 comments

Comments

@ledm
Copy link
Collaborator

ledm commented May 6, 2022

Just thinking that there are probably several difference "analysis" tools out there, but only one bgcval (well, two now!). If would be more obvious what we're doing if we changed the commands from analysis_timeseries to bgcval_timeseries.

Just a thought. Might be an easy fix. Thoughts @valeriupredoi? Probably better to do it now before we write too much documentation/tutorials...

@valeriupredoi
Copy link
Owner

sounds good - up to you, man, just careful with the imports after wards 😁

@ledm
Copy link
Collaborator Author

ledm commented Aug 4, 2022

This would be a good change to make before we share it with the others.

@ledm ledm mentioned this issue Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants