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

Methane demands exceed methane available #157

Closed
ekluzek opened this issue Dec 16, 2017 · 1 comment
Closed

Methane demands exceed methane available #157

ekluzek opened this issue Dec 16, 2017 · 1 comment
Labels
closed: wontfix We won't fix this issue, because it would be too difficult and/or isn't important enough to fix
Milestone

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Dec 16, 2017

Erik Kluzek < erik > - 2016-12-22 15:58:38 -0700
Bugzilla Id: 2394
Bugzilla CC: cdkoven, dlawren, oleson, rfisher,

This is with the SMS_Lm25.f19_g16.ICLM45BGCCROP.yellowstone_gnu.clm-cropMonthOutput test with transcrop_n05_clm4_5_13_r210 after time-step 208...

  89: ENDRUN: ERROR: Methane demands exceed methane available.ERROR in /glade/p/work/erik/clm_transcrop/components/clm/src/biogeochem/ch4Mod.F90 at line 3418                                                                                                                                                                                                                                                                                                                                                                                                
  89: ERROR: Unknown error submitted to shr_sys_abort.
  74: Methane demands exceed methane available. Error in methane competition (mol/m^3/s), c,j:  -1.5575315045230422E-009       33170           2
  74: Latdeg,Londeg=   8.5263157894735997        80.000000000000000
  74: ENDRUN: ERROR: Methane demands exceed methane available.ERROR in /glade/p/work/erik/clm_transcrop/components/clm/src/biogeochem/ch4Mod.F90 at line 3418

with stack trace...

89:#0  0x2B80A405EB57
74:#0  0x2B8377A15B57
89:#1  0x9E7BF9 in __shr_sys_mod_MOD_shr_sys_backtrace
89:#2  0x9E7F52 in __shr_sys_mod_MOD_shr_sys_abort
89:#3  0x4A1542 in __abortutils_MOD_endrun_vanilla
89:#4  0x7A7DB2 in __ch4mod_MOD_ch4_tran at ch4Mod.F90:0
89:#5  0x7BE1F9 in __ch4mod_MOD_ch4
89:#6  0x4A80A9 in __clm_driver_MOD_clm_drv
89:#7  0x49D2FB in __lnd_comp_mct_MOD_lnd_run_mct
89:#8  0x41D893 in __component_mod_MOD_component_run
74:#1  0x9E7BF9 in __shr_sys_mod_MOD_shr_sys_backtrace
89:#9  0x40B658 in __cesm_comp_mod_MOD_cesm_run
@ekluzek ekluzek added this to the clm5 milestone Dec 16, 2017
@ekluzek ekluzek modified the milestones: clm5, future Jan 19, 2018
@billsacks
Copy link
Member

Closing since we haven't seen this problem in a while.

@billsacks billsacks added closed: wontfix We won't fix this issue, because it would be too difficult and/or isn't important enough to fix and removed severity: critical labels Nov 26, 2018
samsrabin pushed a commit to samsrabin/CTSM that referenced this issue May 3, 2024
* added skip_restart_read logic needed for CTSM spin-up runs
* fixes for getting streams with vector fields to work correctly
Co-authored-by: Jim Edwards <jedwards@ucar.edu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: wontfix We won't fix this issue, because it would be too difficult and/or isn't important enough to fix
Projects
None yet
Development

No branches or pull requests

2 participants