Enhance TCI use case to be flexible for other models besides CESM #2575
Labels
priority: high
High Priority
requestor: University/other
University Collaborator, not otherwise specified
type: enhancement
Improve something that it is currently doing
Milestone
Describe the Enhancement
In #2388, this use case was updated to use raw FLUXNET observations to compute TCI. Some refinements were made to the use case config file as well, but the names selected for configuration items are specific to
CESM
. This issue is to generalize the config items and add documentation for the use case describing how a user would modify the config file to work for their model. The changes should be specific to items related to computing TCI only, and not about file formats, grids, or other config options that are specific to the users' model.We should also at the same time:
season
being processed to theDESC
column so a user can filter output in downstream tools by seasonPOINT_STAT_OBS_VALID_BEG
andOBS_VALID_BEG
are being used.POINT_STAT_OBS_VALID_BEG
is provided on the command line and overridesOBS_VALID_BEG
.Time Estimate
4 hours
Funding Source
UWCIMSS Otkin Drought 2785031
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
Enhancement Checklist
See the METplus Workflow for details.
Branch name:
feature_<Issue Number>_<Description>
Pull request:
feature <Issue Number> <Description>
Select: Reviewer(s) and Development issues
Select: Repository level development cycle Project for the next official release
Select: Milestone as the next official version
The text was updated successfully, but these errors were encountered: