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

Et data #120

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Et data #120

wants to merge 2 commits into from

Conversation

jrmodel
Copy link

@jrmodel jrmodel commented Dec 17, 2022

use the updated version

@codecov-commenter
Copy link

Codecov Report

Base: 69.47% // Head: 69.47% // No change to project coverage 👍

Coverage data is based on head (cdf9820) compared to base (4b84ff4).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #120   +/-   ##
=======================================
  Coverage   69.47%   69.47%           
=======================================
  Files          36       36           
  Lines        4282     4282           
=======================================
  Hits         2975     2975           
  Misses       1307     1307           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@khufkens
Copy link
Member

khufkens commented Jan 4, 2023

Hi @stineb, should this be integrated now or how do we go about this. There don't seem to be any breaking changes (tests still pass - if not adjusted).

@stineb
Copy link
Collaborator

stineb commented Jan 4, 2023

It's not clear to me what is new in the branch jrmodel:ET_data (looking at this).

Whether to merge this or not depends on what we want to have in the rsofun documentation paper. If we keep the scope of that to using GPP and a "trait" (Vcmax) as calibration targets, then we should keep all ET-related developments out of the master branch for now. Therefore, I would not merge this now if it adds anything ET-related (but then, I can't see anything ET-related in commits to this branch).

@khufkens
Copy link
Member

khufkens commented Jan 4, 2023

Fine with me. Will keep this open. @jrmodel keep your fork in sync (see sync button) to make this easier upstream if other changes to the main branch.
Screenshot from 2023-01-04 14-28-35

@jrmodel
Copy link
Author

jrmodel commented Jan 4, 2023

Fine with me. Will keep this open. @jrmodel keep your fork in sync (see sync button) to make this easier upstream if other changes to the main branch. Screenshot from 2023-01-04 14-28-35

@jrmodel
Copy link
Author

jrmodel commented Jan 4, 2023

Ok. Fine

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

Successfully merging this pull request may close these issues.

None yet

4 participants