ERROR: component_mod:check_fields NaN found in ATM instance

J

jizh

New Member
Hi all,

I am running a simulation of FHIST_BGC with cesm2.1.5. The simulation was initialized from 1900 and the initialization files were from b.e21.BHIST.f09_g17.CMIP6-historical.001 (shared from strandwg ). The sst forcing was based on ERSST shared from asphilli. There are no more changes. The run crashed after ~15years with many errors like:
component_mod:check_fields NaN found in ATM instance: 1 field Faxa_bcphiwet
1d global index: 31951

I found similar errors in this forum mainly were caused by CLM forcing data, but I didn't change them.

Please let me know if anyone has suggestions.

Thank you,
Jian
 

Attachments

Y

yanghh

yanghh
New Member
jizh said:
Hi all,

I am running a simulation of FHIST_BGC with cesm2.1.5. The simulation was initialized from 1900 and the initialization files were from b.e21.BHIST.f09_g17.CMIP6-historical.001 (shared from strandwg ). The sst forcing was based on ERSST shared from asphilli. There are no more changes. The run crashed after ~15years with many errors like:
component_mod:check_fields NaN found in ATM instance: 1 field Faxa_bcphiwet
1d global index: 31951

I found similar errors in this forum mainly were caused by CLM forcing data, but I didn't change them.

Please let me know if anyone has suggestions.

Thank you,
Jian
Click to expand...
Hi Jian,

I’m encountering a very similar issue with FHIST(f19f19mg17) case in CESM2.1.5. I also get NaN errors related to Faxa_bcphiwet, and I haven’t changed the CLM forcing either. I was wondering if you eventually found the cause or managed to solve it. If so, could you please share how you resolved it? Any suggestions would be greatly appreciated.
In my case, I started the run from 1950; it runs normally for one or two years, but then I hit NaN values. The cesm.log shows errors such as:


ERROR: component_mod:check_fields NaN found in ATM instance: 1 field Sa_z 1d global index: 11775
ERROR: component_mod:check_fields NaN found in ATM instance: 1 field Sa_z 1d global index: 11631
ERROR: component_mod:check_fields NaN found in ATM instance: 1 field Faxa_bcphiwet 1d global index: 11921
ERROR: component_mod:check_fields NaN found in ATM instance: 1 field Faxa_bcphiwet 1d global index: 11785
ERROR: component_mod:check_fields NaN found in ATM instance: 1 field Faxa_bcphiwet 1d global index: 11206
ERROR: component_mod:check_fields NaN found in ATM instance: 1 field Sa_z 1d global index: 12067
...
The indices differ, but the pattern seems the same. I was wondering if you eventually found the cause or managed to solve it. If so, could you please share how you resolved it? Any suggestions would be greatly appreciated.
Thanks,
Haihong
 
You must log in or register to reply here.
Back
Top