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

Move fire maps from surface dataset to stream files #2617

Open
samsrabin opened this issue Jun 24, 2024 · 5 comments
Open

Move fire maps from surface dataset to stream files #2617

samsrabin opened this issue Jun 24, 2024 · 5 comments
Assignees
Labels
enhancement new capability or improved behavior of existing capability

Comments

@samsrabin
Copy link
Collaborator

samsrabin commented Jun 24, 2024

As Fang has updated some inputs, it'd be nice to move them to streams files rather than having to update them on all the surface datasets.

  • peatf (peatland fraction)
  • abm (agricultural fire peak month)
  • gdp (gross domestic product)
@ekluzek
Copy link
Collaborator

ekluzek commented Jun 24, 2024

As a starting point you should probably start with the half degree datasets being used by mksurfdata_esmf. That'll provide a nice transition from what's currently being done, to new higher resolution datasets to be used in the future.

Is this change really needed for the Capability freeze? I suppose it might so we don't have to make new surface datasets if updated datasets are required. This might be something good to discuss, so I'll add the next label to it...

@ekluzek ekluzek added the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Jun 24, 2024
@samsrabin samsrabin added the enhancement new capability or improved behavior of existing capability label Jun 24, 2024
@samsrabin
Copy link
Collaborator Author

samsrabin commented Jun 27, 2024

It's only needed for the capability freeze because it needs to happen before I bring in new datasets from Fang—as you said, because I don't want to have to make all new surface datasets for this.

@wwieder
Copy link
Contributor

wwieder commented Jun 27, 2024

These fields should be removed from the 5.3 datasets too, @lawrencepj1 and @slevis-lmwg.

@samsrabin samsrabin removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Jun 27, 2024
@ekluzek
Copy link
Collaborator

ekluzek commented Aug 15, 2024

We will include the new data on the ctsm5.3.0 surface datasets. But, after ctsm5.3.0 this change will come in which will enable clm4_5 and clm5_0 to be closer to what they were previous ctsm5.3.0.

@samsrabin
Copy link
Collaborator Author

These will be available on the half-degree surface datasets produced from #2500.

@samsrabin samsrabin moved this from Todo (BY CHILL) to Todo (post-chill) in CTSM: Fire updates 2024 Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new capability or improved behavior of existing capability
Projects
Status: Todo (post-chill)
Development

No branches or pull requests

3 participants