Updates for the SOCA config for updating pinned JEDI build #430
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.
Following some SABER updates, configuration for SOCA needs to be updated to use JEDI builds past Aug 3rd.
Explicit_diffusion
became generic (i.e., it can be shared with other models). For SOCA, it has to use the model interface and that introduces some quirks. The correlation scales need to be named as ocean model variables (instead ofhz
orvt
,tocn
andssh
). And thestate_variable
inbackground_diffusion_vt.yaml
has to only contain the correlation scale variable (tocn
in this case). Hopefully this will be fixed in a future update.Dependencies:
Requires a new build, which I already did for August 31st and works for that. So we should first wait for Pinned versions utilities and abort suppression #429@rtodling tested with an August 31st JEDI build and results are practically identical.
Requires Static file changes which are currently located in my local folder.