forked from E3SM-Project/E3SM
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Full Wave Momentum Coupling #104
Open
erinethomas
wants to merge
297
commits into
E3SM-Ocean-Discussion:master
Choose a base branch
from
erinethomas:WaveMomentumCoupling
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Full Wave Momentum Coupling #104
erinethomas
wants to merge
297
commits into
E3SM-Ocean-Discussion:master
from
erinethomas:WaveMomentumCoupling
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
share/util/shr_flux_mod.F90
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line 139: Add comment about cor30a-wav
erinethomas
force-pushed
the
WaveMomentumCoupling
branch
from
July 10, 2024 20:45
bc5368e
to
e0f6b26
Compare
vanroekel
reviewed
Jul 26, 2024
lines.append('<stream name="timeSeriesStatsDailyWaveOutput"') | ||
lines.append(' type="output"') | ||
lines.append(' precision="single"') | ||
lines.append(' io_type="pnetcdf"') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from a discussion with @sbrus89 suggest changing the io_type toio_type="{}"'.format(ocn_pio_typename)
erinethomas
force-pushed
the
WaveMomentumCoupling
branch
from
August 8, 2024 15:34
2a838fd
to
9b7fe62
Compare
…c_dev_kokkos_ekat Initial Kokkos Dev Documentation
…nger/split_output_setup Automatically Merged using E3SM Pull Request AutoTester PR Title: I/O: Split OutputManager creation from setup PR Author: tcclevenger PR LABELS: I/O, AT: AUTOMERGE
This commit removes a docker container that was added to EAMxx for the Corrective-ML effort. Since that effort is on pause and there may be future efforts to containerize the code this commit removes this version to avoid confusion.
…/update_eamxx_testing_docs Automatically Merged using E3SM Pull Request AutoTester PR Title: Update EAMxx docs and improve help formatters PR Author: jgfouca PR LABELS: AT: AUTOMERGE, AT: Integrate Without Testing
…time-params p3 runtime params reorg
…nahue/remove_old_docker_folder Automatically Merged using E3SM Pull Request AutoTester PR Title: This commit removes a docker folder in eamxx no longer in use. PR Author: AaronDonahue PR LABELS: AT: AUTOMERGE, AT: Integrate Without Testing, code cleanup
…/p3/3048-improve-p3-runtime-struct Automatically Merged using E3SM Pull Request AutoTester PR Title: clarify P3Runtime struct defaults PR Author: mahf708 PR LABELS: BFB, p3, AT: AUTOMERGE
…/eamxx/flush-output-with-rhist Automatically Merged using E3SM Pull Request AutoTester PR Title: A couple of fixes and an addition for IO PR Author: bartgol PR LABELS: enhancement, I/O, AT: AUTOMERGE, bugfix
…h/rrm_update_markdown Automatically Merged using E3SM Pull Request AutoTester PR Title: change RRM docs to point from scream-docs to eamxx-scripts PR Author: bogensch PR LABELS: AT: AUTOMERGE, documentation, AT: Integrate Without Testing
i.e. wav_ocn_coup = 'none', 'one', or 'two' for no coupling, one way coupling (ocn to wav), or full two way coupling
…nvil Pe layout for B case with waves
…s analysis member calculations)
erinethomas
force-pushed
the
WaveMomentumCoupling
branch
from
November 12, 2024 16:11
a174729
to
0e192e6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NEW WAVE MOMENTUM COUPLING FEATURE
Full momentum coupling between WW3, MPAS-Ocean, and EAM is being implemented.
This discussion is for the purpose of getting a preliminary code review and feedback before an official PR is opened into E3SM.
This PR uses COARE3.0 flux calculation which is needed for wave coupling to atmosphere via charnock parameter.
A table summarizing all testing being performed is at the bottom of the page here:
https://acme-climate.atlassian.net/wiki/spaces/OO/pages/4271702034/2024.Q2+WAVEWATCH+III+maintenance+developments
Suggestions welcome for additional testing that is needed to open a PR into E3SM.
a 100 year Fully coupled Simulation is currently being done.
The use of WW3 is 'stealth' in that WW3 is NOT a standard component of E3SM for production runs. However, the implementation of wave-ocean-atm coupling in this PR defines the default coupling based upon the COMPSET used.
For example, a fully coupled base with active waves (B compset + WW3) will assume full, two-way coupling between WW3-EAM-MPASO and MPAS-SI. (note: limited wave-ice coupling for now, full wave-ice coupling coming in near future). On the other hand, if a data atmosphere used, like in a G Case+WW3, EAM-WW3 coupling will default to "one-way" (data winds passed to WW3) while full two way coupling is used between the active components of WW3 and MPAS-O/MPAS-SI.