The information contained in the cism restart files only allow the time manager to restart properly if the last run stopped at a day boundary. For POP, seconds_this_day is written to the restart file, but that isn't done for cism; I believe that is the cause of the problem.
Once this is fixed, a unit test should be added to test this capability in test/unit/time_management.
While fixing this bug, we should also look for other time management-related quantities that are in the pop restart file but not the cism restart file.
At some point, we should ditch the current time manager and put in place a simpler and more robust time manager, in order to fix this and other limitations of the current time manager.
Bill Sacks < sacks > - 2011-12-14 10:27:05 -0700 Bugzilla Id: 1441 Bugzilla CC: erik, lipscomb, mvertens,
The information contained in the cism restart files only allow the time manager to restart properly if the last run stopped at a day boundary. For POP, seconds_this_day is written to the restart file, but that isn't done for cism; I believe that is the cause of the problem.
Once this is fixed, a unit test should be added to test this capability in test/unit/time_management.
While fixing this bug, we should also look for other time management-related quantities that are in the pop restart file but not the cism restart file.