Skip to content

Conversation

@ph-kev
Copy link
Member

@ph-kev ph-kev commented Dec 9, 2025

This updates ClimaDiagnostics to v0.3. The only breaking change is that the diagnostics are saved at the start of the reduction period instead of at the end.

I don't think this affects anything, but the postprocessing of the NetCDF files. I couldn't find any postprocessing of the diagnostics that depends on the exact time values beside the calibration.

In general, any plots with instantaneous variables should be unchanged, but any plots with time reduction should differ by single time period. For example, a plot with time = 8d would change to time = 7d if the time reduction is daily.

ClimaDiagnostics v0.2.13 is still supported, because ClimaCoupler does not support v0.3 yet.

@ph-kev
Copy link
Member Author

ph-kev commented Jan 20, 2026

@costachris This will break the gcm_driven_scm experiment (https://github.com/CliMA/ClimaAtmos.jl/tree/main/calibration/experiments/gcm_driven_scm), but I can't tell if this experiment is still in use. Should this experiment be updated to support ClimaDiagnostics v0.3?

@ph-kev ph-kev requested a review from juliasloan25 January 20, 2026 21:44
Copy link
Member

@juliasloan25 juliasloan25 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me! I would just want to hear from Costa about the experiment you mentioned before merging.

@szy21 can we tag a patch release so we can update the coupler too, or should we wait since things are broken right now?

@szy21
Copy link
Member

szy21 commented Jan 20, 2026

This looks good to me! I would just want to hear from Costa about the experiment you mentioned before merging.

@szy21 can we tag a patch release so we can update the coupler too, or should we wait since things are broken right now?

We can tag but it will be a breaking release because of this: #4198. Maybe we can tag a release when the coupler surface flux PR is ready?

@juliasloan25
Copy link
Member

This looks good to me! I would just want to hear from Costa about the experiment you mentioned before merging.
@szy21 can we tag a patch release so we can update the coupler too, or should we wait since things are broken right now?

We can tag but it will be a breaking release because of this: #4198. Maybe we can tag a release when the coupler surface flux PR is ready?

Sounds good. Teja and I are also working on updating the Makie compats in ClimaCore/ClimaAtmos/ClimaLand. It will be good to make releases of those packages when those are in too

@szy21
Copy link
Member

szy21 commented Jan 20, 2026

This looks good to me! I would just want to hear from Costa about the experiment you mentioned before merging.
@szy21 can we tag a patch release so we can update the coupler too, or should we wait since things are broken right now?

We can tag but it will be a breaking release because of this: #4198. Maybe we can tag a release when the coupler surface flux PR is ready?

Sounds good. Teja and I are also working on updating the Makie compats in ClimaCore/ClimaAtmos/ClimaLand. It will be good to make releases of those packages when those are in too

Sounds good. We can tag the next minor release after all of these are done.

Copy link
Member

@nefrathenrici nefrathenrici left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. @costachris can chime in, but I think we should add ClimaDiagnostics and a compat "=0.2.15" to the calibration experiment Project.toml. That should help keep the pipeline reproducible.

@costachris
Copy link
Member

We do still use gcm_driven_scm so pinning "=0.2.15" as Nat suggested sounds good to me!

@ph-kev ph-kev force-pushed the kp/update-diag branch 2 times, most recently from 53a69af to ac3e89f Compare January 21, 2026 19:19
@ph-kev ph-kev requested a review from costachris January 21, 2026 19:20
Comment on lines +23 to +25
ClimaAtmos = "=0.27.6"
ClimaCalibrate = "=0.1.4"
ClimaDiagnostics = "=0.2.15"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wasn't sure about the versions of the packages. I don't think there was anything breaking going from ClimaCalibrate 0.0.3 to 0.1.4.

cc: @nefrathenrici

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants