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

Error handling for monthly mean History collection when run duration <1 month #1606

Closed
lizziel opened this issue Jul 19, 2022 · 2 comments
Closed
Assignees
Labels
🪲 Bugfix This fixes a bug!

Comments

@lizziel
Copy link
Contributor

lizziel commented Jul 19, 2022

I am encountering the following ESMF log error after modifying my HISTORY.rc file in GCHP 14.0 (uses MAPL 2.18.3) and reducing run duration to 1hr.

20220719 134413.379 ERROR            PET00 ESMCI_TimeInterval.C:1340 ESMCI::TimeInterval::operator/(t Invalid argument  - can't divide without startTime or endtime
20220719 134413.380 ERROR            PET00 ESMCI_TimeInterval.C:1340 ESMCI::TimeInterval::operator/(t Invalid argument  - can't divide without startTime or endtime
20220719 134414.927 INFO             PET00 ESMCI_Clock.C:2036 ESMCI::Clock::addAlarm() For clock ApplClock, alarm list is full (200 alarms), re-allocating to hold 400 alarms.
20220719 134415.252 INFO             PET00 ESMCI_Clock.C:2036 ESMCI::Clock::addAlarm() For clock ApplClock, alarm list is full (400 alarms), re-allocating to hold 600 alarms.
20220719 134415.260 INFO             PET00 ESMCI_Clock.C:2036 ESMCI::Clock::addAlarm() For clock ApplClock, alarm list is full (600 alarms), re-allocating to hold 800 alarms.
20220719 134415.267 INFO             PET00 ESMCI_Clock.C:2036 ESMCI::Clock::addAlarm() For clock ApplClock, alarm list is full (800 alarms), re-allocating to hold 1000 alarms.
20220719 134415.406 INFO             PET00 ESMCI_Clock.C:2036 ESMCI::Clock::addAlarm() For clock ApplClock, alarm list is full (1000 alarms), re-allocating to hold 1200 alarms.
20220719 134415.414 INFO             PET00 ESMCI_Clock.C:2036 ESMCI::Clock::addAlarm() For clock ApplClock, alarm list is full (1200 alarms), re-allocating to hold 1400 alarms.
20220719 134415.691 INFO             PET00 ESMCI_Clock.C:2036 ESMCI::Clock::addAlarm() For clock ApplClock, alarm list is full (1400 alarms), re-allocating to hold 1600 alarms.
20220719 134415.700 INFO             PET00 ESMCI_Clock.C:2036 ESMCI::Clock::addAlarm() For clock ApplClock, alarm list is full (1600 alarms), re-allocating to hold 1800 alarms.
20220719 134415.709 INFO             PET00 ESMCI_Clock.C:2036 ESMCI::Clock::addAlarm() For clock ApplClock, alarm list is full (1800 alarms), re-allocating to hold 2000 alarms.
20220719 134415.761 INFO             PET00 ESMCI_Clock.C:2036 ESMCI::Clock::addAlarm() For clock ApplClock, alarm list is full (2000 alarms), re-allocating to hold 2200 alarms.

I traced the issue to a new time-averaged collection that had monthly mean enabled. All other collections had monthly mean disabled.

  StratBM.template:       '%y4%m2%d2_%h2%n2z.nc4',
  StratBM.format:         'CFIO',
  StratBM.timestampStart: .true.
  StratBM.monthly:        1
  StratBM.frequency:      010000
  StratBM.duration:       010000
  StratBM.mode:           'time-averaged'
  StratBM.fields:         'SpeciesConc_NO2 ', 'GCHPchem',

When I disable monthly mean in the new collection the issue goes away (no ESMF error log files are generated).

  StratBM.template:       '%y4%m2%d2_%h2%n2z.nc4',
  StratBM.format:         'CFIO',
  StratBM.timestampStart: .true.
  StratBM.monthly:        0
  StratBM.frequency:      010000
  StratBM.duration:       010000
  StratBM.mode:           'time-averaged'
  StratBM.fields:         'SpeciesConc_NO2 ', 'GCHPchem',

This error does not crash the run, but I wonder if there should be error handling in MAPL for the case of monthly mean turned on when duration is less than a month? If you would rather have it ignored, could you update it so that the ESMF error does not get triggered?

@lizziel lizziel added the 🪲 Bugfix This fixes a bug! label Jul 19, 2022
@mathomp4
Copy link
Member

@lizziel I believe this is a bug (#1495) that we fixed with #1496 which is in MAPL 2.21 (put in 2.21.0 specifically).

I suppose the question for you is: can you update to MAPL 2.21? Or do you need to stay with the 2.18 releases? If so, we'd need to backport that patch for you into a 2.18.4, I guess.

(And I guess I'd want to consult with @atrayano if there are any other monthly collection fixes we've fixed since 2.18.3.)

@lizziel
Copy link
Contributor Author

lizziel commented Jul 20, 2022

Ah, good to know! Clearly I have not been reading all the release notes. This isn't a big problem for us so I'll wait for the next MAPL upgrade which I'll probably do in the fall.

@lizziel lizziel closed this as completed Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🪲 Bugfix This fixes a bug!
Projects
None yet
Development

No branches or pull requests

3 participants