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

Update conditions for Southern Ocean ice and river runoff removal #6693

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

cbegeman
Copy link
Contributor

@cbegeman cbegeman commented Oct 16, 2024

This PR modifies the conditions for river and ice runoff removal in E3SM cases. This changes the behavior of E3SM cases where data icebergs (DIB) or ice-shelf melting (ISMF) were active and thus doesn't not affect water cycle simulations.

River runoff

  • Previous behavior: never removed
  • New behavior: removed when atmosphere is not active and ice shelf melt fluxes are on

Ice runoff

  • Previous behavior: removed when DIB is on and atmosphere is not active
  • New behavior: removed when DIB is on

[BFB] when DIB and DISMF are inactive (all WC configurations)
[non-BFB] when DIB or DISMF are active

@cbegeman cbegeman added mpas-ocean non-BFB PR makes roundoff changes to answers. BFB PR leaves answers BFB and removed non-BFB PR makes roundoff changes to answers. labels Oct 16, 2024
@cbegeman cbegeman added non-BFB PR makes roundoff changes to answers. and removed BFB PR leaves answers BFB labels Oct 17, 2024
@xylar
Copy link
Contributor

xylar commented Oct 17, 2024

Great, thanks @cbegeman! I'll run a few quick tests with various combinations of G and B cases and with or without DIB and DISMF

@cbegeman
Copy link
Contributor Author

Testing

I have run a comparison between this branch and master with the e3sm_cryo_developers suite on chrys with intel, impi.

The result was NLFAIL ${TEST_NAME} (but otherwise OK) RUN for all tests. In each case, the master namelist included

config_remove_ais_ice_runoff = .false.
config_remove_ais_river_runoff = .false.

whereas for this branch those options are

config_remove_ais_ice_runoff = .true.
config_remove_ais_river_runoff = .true.

@cbegeman
Copy link
Contributor Author

@xylar If you could run a few tests other than the ones in the cryo dev suite or tests with a different machine, compiler combo than chrys, intel, impi that would be great!

@xylar
Copy link
Contributor

xylar commented Oct 17, 2024

Okay, I'll do that.

I don't think I would have expected the cryo developer tests to be BFB. Was that a surprise to you, too?

@cbegeman
Copy link
Contributor Author

I don't think I would have expected the cryo developer tests to be BFB. Was that a surprise to you, too?

Yes, it was. There are both CORE-IAF and JRA-forced runs in the suite and both should have river runoff and JRA should have ice runoff. Do you think these tests could just be too short?

@xylar
Copy link
Contributor

xylar commented Oct 17, 2024

Do you think these tests could just be too short?

I wouldn't have thought so. I think they run for ~5 days, which should be long enough for removed runoff to affect ocean T and S. But maybe not fields the coupler sees? If not, that would be disconcerting!

This may point to another situation (G cases) where the fact that we don't look at MPAS-Ocean or -Seaice history files is a disaster waiting to happen.

@jonbob, do you have thoughts on this?

@jonbob
Copy link
Contributor

jonbob commented Oct 17, 2024

We usually see impacts in the cpl fields, but not always. But I would expect those tests to be non-BFB. Have we run longer comparisons? I don't see any referenced in this PR

@xylar
Copy link
Contributor

xylar commented Oct 17, 2024

No, we haven't. We presumably need to run a longer Icos G case with master and with this to show that we're not seeing unexpected differences. That would be certain to be non-BFB.

@xylar
Copy link
Contributor

xylar commented Oct 17, 2024

I can get that going.

@jonbob
Copy link
Contributor

jonbob commented Oct 17, 2024

I think it would be necessary to document the impact of this PR

@xylar
Copy link
Contributor

xylar commented Oct 17, 2024

@jonbob, would a 10-year G-case be sufficient? I would think so.

@jonbob
Copy link
Contributor

jonbob commented Oct 17, 2024

@xylar -- I agree, a 10-year G-case comparison would be perfect

@cbegeman
Copy link
Contributor Author

@xylar Thanks for doing that test!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mpas-ocean non-BFB PR makes roundoff changes to answers.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants