Off by one timestep for diagnostics when restarting

[ph-kev]

For this buildkite run where a restart was used, the diagnostics produced from the restarted simulation are off by one coupler timestep. For this run, the times of the diagnostics are shifted by two minutes or one coupler timestep.

To reproduce this bug, you can

1. Run the simulation and create a checkpoint (simulation time at checkpoint should be in sync with diagnostics output schedule)
2. Restart from the checkpoint

This happens when restarting from both state and state + cache.

[ph-kev]

I can replicate this bug with only a ClimaAtmos simulation from restarting from the state.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• Some nsight jobs have error codes 139 #3375
• MPI restart tests occasionally hang #3381
• EDMFX ERA5 ExternalDrivenTVForcing test case slowing down #3899
• test_restart fails when using cloud_model: grid_scale and turbconv: nothing #4163
• Error starting from restart without atoms_model_hash #3387

👤 Suggested Assignees

• charleskawczynski
• Sbozzolo
• nefrathenrici
• szy21
• haakon-e

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!