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

NEON AG sites are running with generic crop rather than prognostic crop #1889

Closed
ekluzek opened this issue Nov 2, 2022 · 7 comments · Fixed by #1872
Closed

NEON AG sites are running with generic crop rather than prognostic crop #1889

ekluzek opened this issue Nov 2, 2022 · 7 comments · Fixed by #1872
Labels
bug something is working incorrectly science Enhancement to or bug impacting science

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Nov 2, 2022

Brief summary of bug

NEON crop sites such as SJER run with generic crop rather than prognostic crop.

General bug information

CTSM version you are using: ctsm5.1.dev113

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

Configurations affected: NEON agriculture sites

Details of bug

Both run_neon and compsets such as I1PtClm51Bgc and IHist1PtClm51Bgc run with prognostic crop off. This is fine for most NEON sites as it doesn't matter, since they don't have any crop vegetation. But, the agriculture sites probably should run with prognostic crop on. So they need to use a different compset, or need to explicitly turn crop on.

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

./run_neon.py --setup-only --overwrite --neon-site SJER --run-type ad

Important output or errors that show the problem

It runs without error, but use_crop is off, which means that it will be using generic crop in place of prognostic crop types.

@ekluzek
Copy link
Collaborator Author

ekluzek commented Nov 2, 2022

It looks like the NEON sites that should run with prognostic crop are

KONA = 19
STER = 19

(edited to fix the list)

@ekluzek
Copy link
Collaborator Author

ekluzek commented Nov 2, 2022

Looks like the SJER surface dataset is pointing to the wrong PFT type. It's pointing to c3_non-arctic_grass, but should be pointing to temperate_crop. So it's not even running with a generic crop.

(This statement was incorrect).

@negin513
Copy link
Contributor

negin513 commented Nov 2, 2022

Hello @ekluzek. Not sure about the new datasets created recently. But for the older surface datasets, first I used --crop in subset_data and then I additionally put in some checks for AG sites specifically :

# -- updates for ag sites : KONA and STER
ag_sites = ["KONA", "STER"]
if site_name in ag_sites:
print("Updating PCT_NATVEG")
print("Original : ", f2.PCT_NATVEG.values)
f2.PCT_NATVEG.values = [[0.0]]
print("Updated : ", f2.PCT_NATVEG.values)
print("Updating PCT_CROP")
print("Original : ", f2.PCT_CROP.values)
f2.PCT_CROP.values = [[100.0]]
print("Updated : ", f2.PCT_CROP.values)
print("Updating PCT_NAT_PFT")
#print (f2.PCT_NAT_PFT)
print(f2.PCT_NAT_PFT.values[0])
f2.PCT_NAT_PFT.values[0] = [[100.0]]
print(f2.PCT_NAT_PFT[0].values)

At the time these were the only AG sites we had data for. So maybe we should add the other AG sites here.

@negin513
Copy link
Contributor

negin513 commented Nov 2, 2022

Here is the issue about KONA and STER: #1606 was fixed in #1461
Also #1871 points to similar thing.

@ekluzek
Copy link
Collaborator Author

ekluzek commented Nov 2, 2022

Ahh, @negin513 thanks for that! I was reading the wrong column of neon_sites_dompft.csv! Looks like the AG sites are still just KONA and STER. It does look like the latest datasets are still not right for those two though. It looks like it was run through modify_singlept_site_neon.py by @wwieder though, so I'm not sure what's up there.

@ekluzek
Copy link
Collaborator Author

ekluzek commented Nov 2, 2022

Ahh, wait -- no the surface datasets are correct! Sorry. The general issue of not running prognostic crop for these two is still there though. But, the surface datasets are correct.

@wwieder
Copy link
Contributor

wwieder commented Nov 3, 2022

Looks like you have this straightened out correctly in the updated file @ekluzek . @negin513 thanks for clarifying this quickly.

@samsrabin samsrabin added bug something is working incorrectly science Enhancement to or bug impacting science labels Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something is working incorrectly science Enhancement to or bug impacting science
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants