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

PEcAn 2.0 list of non-backward compatible changes #392

Open
1 of 7 tasks
dlebauer opened this issue Mar 21, 2015 · 4 comments
Open
1 of 7 tasks

PEcAn 2.0 list of non-backward compatible changes #392

dlebauer opened this issue Mar 21, 2015 · 4 comments

Comments

@dlebauer
Copy link
Member

dlebauer commented Mar 21, 2015

Package names

all suggestions can be discussed in comments; checked when finalized

Function names

Other Conventions

Variable names

  • implement consistent use of CF style variable names?
    • Deprecate use of MsTMIP (from @mdietze)?

reorganization

@dlebauer dlebauer added this to the 2.0 Major Version Bump milestone Mar 21, 2015
dlebauer added a commit that referenced this issue Mar 21, 2015
dlebauer referenced this issue Apr 23, 2015
@mdietze mdietze removed this from the 2.0 Major Version Bump milestone Jan 12, 2016
@ashiklom
Copy link
Member

ashiklom commented Oct 26, 2018

A few BETY-related changes I'd like to see, while they're fresh on my mind:

  • Remove the restriction that sites require citations.
  • Remove the restriction on author length for citations (BETY PR 573 has been open for ages)
  • Add status as a column in the BETY workflows (and runs?) table. Could be a JSON(-binary) field to give us flexibility. That would make it easier to check the status of workflows, and would dramatically accelerate the rendering of our History page (which IIRC currently parses the STATUS text file of every run) .

@robkooper
Copy link
Member

@github-actions
Copy link

github-actions bot commented May 1, 2020

This issue is stale because it has been open 365 days with no activity.

@Aariq
Copy link
Collaborator

Aariq commented Jul 19, 2022

A suggestion: make it more clear from function names which functions return objects and which are called for their side-effects. E.g. get.trait.data() and do_conversions() return a modified settings object but run.meta.analysis() and model2netcdf.ED2() are called for side-effects. Maybe set_* for things that modify settings and run_* or write_* for functions called for side-effects?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants