You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a number of new features that have been added to the model recently that should be documented in the tech note and user's guide. I've started a short list of these and tried to suggest people who can help with this. Maybe at an upcoming meeting we can discuss how to efficiently get these contributions into our documentation?
@wwieder Tech note documentation writeup was included in the #1787. See the Snow and Soil Temperatures section at master. If you want a user-guide write-up for the feature, i can make a quick PR with that.
Thanks @mvdebolskiy, that's excellent! do we just have to 'build' the tech note again for these to changes to show up on the wiki? Is there additional, practical information that should be included in the user's guide for excess ice? I'm not familiar with how to run with this feature?
@samsrabin I'm not sure if the crop calendar work belongs with other crop model documentation or under [special cases in the user's guide]? Are the crop calendars not going to be on by default for CTSM5.1 crop simulations?
That's right, @wwieder. All I've done so far is add prescribed static crop calendars, which of course don't allow prognostic seasonal shifts. So "special cases" is probably more appropriate.
Thanks @mvdebolskiy, that's excellent! do we just have to 'build' the tech note again for these to changes to show up on the wiki?
Yes.
Is there additional, practical information that should be included in the user's guide for excess ice? I'm not familiar with how to run with this feature?
Might be. I can add an entry to the "Run with special cases" about how initialization works and additional spinup required. However, it's described in the papers linked in the tech note.
@wwieder I am happy to contribute to the documentation for the SNICAR updates. Please let me know how I should proceed (e.g., prepare a word doc and send it to the CTSM team?) and when you will need it. Thanks!
@wwieder Do we want to add a new tech note section (eg, 2.33) for running with NEON? I'm not sure that it would fit under other pre-existing sections. I'd be happy to put something together for run_neon in general, as well as including some PRISM details, and make a PR to update the tech note.
Can you clarify where in the user's guide you would want this?
I think we need to have a discussion about the crop calendars and how we
will be using this feature going forward. Due to the large biases in some
regions in crop planting dates in CLM5, I think it is a big priority to
include a crop planting calendar for CTSM6, perhaps even if we do not allow
prognostic seasonal shifts. Or, maybe a very simple parameterization
allowing for a shifting crop planting date could be implemented.
Activity
mvdebolskiy commentedon Aug 18, 2023
@wwieder Tech note documentation writeup was included in the #1787. See the Snow and Soil Temperatures section at master. If you want a user-guide write-up for the feature, i can make a quick PR with that.
samsrabin commentedon Aug 18, 2023
Agreed. Should my things go under "Running with special cases," then?
wwieder commentedon Aug 18, 2023
Thanks @mvdebolskiy, that's excellent! do we just have to 'build' the tech note again for these to changes to show up on the wiki? Is there additional, practical information that should be included in the user's guide for excess ice? I'm not familiar with how to run with this feature?
@samsrabin I'm not sure if the crop calendar work belongs with other crop model documentation or under [special cases in the user's guide]? Are the crop calendars not going to be on by default for CTSM5.1 crop simulations?
samsrabin commentedon Aug 18, 2023
That's right, @wwieder. All I've done so far is add prescribed static crop calendars, which of course don't allow prognostic seasonal shifts. So "special cases" is probably more appropriate.
mvdebolskiy commentedon Aug 18, 2023
Yes.
Might be. I can add an entry to the "Run with special cases" about how initialization works and additional spinup required. However, it's described in the papers linked in the tech note.
cenlinhe commentedon Aug 18, 2023
@wwieder I am happy to contribute to the documentation for the SNICAR updates. Please let me know how I should proceed (e.g., prepare a word doc and send it to the CTSM team?) and when you will need it. Thanks!
TeaganKing commentedon Aug 18, 2023
@wwieder Do we want to add a new tech note section (eg, 2.33) for running with NEON? I'm not sure that it would fit under other pre-existing sections. I'd be happy to put something together for run_neon in general, as well as including some PRISM details, and make a PR to update the tech note.
Can you clarify where in the user's guide you would want this?
dlawrenncar commentedon Aug 18, 2023
samsrabin commentedon Aug 18, 2023
Definitely agree, @dlawrenncar. I'll send you et al. an email. For now, I have some ideas for "easy [prognostic] wins" in issue #1928.
dmleung commentedon Aug 18, 2023
Hi, I can write the dust updates for the tech note too!
mvdebolskiy commentedon Aug 21, 2023
@wwieder Are you making a PR I can contribute to, or should I just make a separate one?
wwieder commentedon Aug 21, 2023
You can make a new one, @mvdebolskiy. thanks.
43 remaining items
samsrabin commentedon May 29, 2025
Closing, as such needs should now be their own issues with a
docs:label.