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

GSSUN and GSSHA are not set on history files #1462

Closed
ekluzek opened this issue Aug 18, 2021 · 1 comment · Fixed by #1497
Closed

GSSUN and GSSHA are not set on history files #1462

ekluzek opened this issue Aug 18, 2021 · 1 comment · Fixed by #1497
Assignees
Labels
bug something is working incorrectly

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Aug 18, 2021

Brief summary of bug

@djk2120 noticed this and has a fix for it.

General bug information

CTSM version you are using: ctsm5.1.dev053

Does this bug cause significantly incorrect results in the model's science? No

Configurations affected: All

Details of bug

GSSHA and GSSUN are set to _FillValue everywhere.

Important details of your setup / configuration so we can reproduce the bug

Most configurations output these two.

@ekluzek ekluzek added the bug something is working incorrectly label Aug 18, 2021
@ekluzek ekluzek self-assigned this Aug 18, 2021
@ekluzek
Copy link
Collaborator Author

ekluzek commented Aug 18, 2021

Note, that part of the reason I'm noting this as a bug is that fixing it get's labeled as an answer change since the history fields are no longer missing everywhere. It labels this as a change in the FillValue, but is a change in answers. So I'll include the fix with other simple answer changes.

ekluzek added a commit to djk2120/CTSM that referenced this issue Aug 18, 2021
ekluzek added a commit to ekluzek/CTSM that referenced this issue Sep 23, 2021
…files with values not just identical to missing value
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something is working incorrectly
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant