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.

Sign up for GitHub

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

Jump to bottom

Add time axis to 1d weight variables in history files #2399

Open
samsrabin opened this issue Mar 5, 2024 · 2 comments
Open

Add time axis to 1d weight variables in history files #2399

samsrabin opened this issue Mar 5, 2024 · 2 comments
Assignees
@samsrabin
Labels
enhancement new capability or improved behavior of existing capability good first issue simple; good for first-time contributors usability Improve or clarify user-facing options

Comments

@samsrabin
Copy link
Collaborator

Various 1-d weight variables, like land1d_wtgcell, change over time. However, they don't get saved with a time axis on the history files, so ncrcat will just give you the first timestep's values. This can be overcome with an additional call of ncecat -u time, but that's annoying and something that new users don't know to do.
@samsrabin samsrabin added enhancement new capability or improved behavior of existing capability tag: simple bfb next this should get some attention in the next week or two. Normally each Thursday SE meeting. labels Mar 5, 2024
@ekluzek ekluzek removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Mar 14, 2024
@samsrabin
Copy link
Collaborator Author

Make sure to NOT do this if the weights aren't time-varying. This saves space in the case where you have a non-transient run with multiple timesteps per file.

@samsrabin
Copy link
Collaborator Author

Changed the "simple bfb" tag to just "simple", since presumably this will change results for one test or another.

@samsrabin samsrabin added the usability Improve or clarify user-facing options label Aug 15, 2024
@samsrabin samsrabin added good first issue simple; good for first-time contributors and removed simple labels Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@samsrabin samsrabin

Labels
enhancement new capability or improved behavior of existing capability good first issue simple; good for first-time contributors usability Improve or clarify user-facing options
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@samsrabin @ekluzek