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

Remove NEMS_DATM component from ufs-weather-model #565

Closed
binli2337 opened this issue May 8, 2021 · 2 comments
Closed

Remove NEMS_DATM component from ufs-weather-model #565

binli2337 opened this issue May 8, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@binli2337
Copy link
Contributor

Description

At this moment, both NEMS_datm and CDEPS are included in ufs-weather-model. The following two tests will be run to evaluate CDEPS in the ufs-weather-model. After satisfactory evaluation of CDEPS is done, the NEMS_datm component will be removed from ufs-weather-model.

Comparison tests:
Test 1) A 60-day run using the mom6_cice6_nems_datm_cmeps model with CFSR forcing
Test 2) A 60-day run using the mom6_cice6_cdeps_datm_cmeps model with CFSR forcing

Solution

After those two tests are run, the results will be evaluated by the marine data assimilation team.

@binli2337 binli2337 added the enhancement New feature or request label May 8, 2021
@binli2337 binli2337 self-assigned this May 8, 2021
@binli2337
Copy link
Contributor Author

The following two runs have been made:

  1. A 60-day run using mom6_cice6_nems_datm with CFSR forcing
  2. A 60-day run using mom6_cice6_cdeps_datm with CFSR forcing

The horizontal grid used in mom6/cice6 is 1 degree tripolar grid.

The model used is the develop branch of ufs-weather-model (May 18, 2021 version, #19e49ec)

The following figures show a few fields from those two runs.

nino34
Fig.1 NINO3.4 SST

SST_60
Fig.2 SST on day 60 of the simulations

ocean_t_day60
Fig.3 Ocean potential temperature on day 60 of the simulations

ocean_s_day60
Fig.4 Ocean salinity on day 60 of the simulations

Fig 5_seaice_thickness
Fig.5 Seaice thickness on day 60 of the simulations

@binli2337
Copy link
Contributor Author

The NEMS_DATM component has been removed from ufs-weather-model ( #845 )

pjpegion pushed a commit to NOAA-PSL/ufs-weather-model that referenced this issue Apr 4, 2023
* update submodule for ccpp/physics: Revert calculation of T2m in NOAH-MP
epic-cicd-jenkins pushed a commit that referenced this issue Apr 17, 2023
…ecast files (#566)

This PR enables running of only the SRW App's deterministic verification (vx) tasks on staged forecast files from previous runs of the App. It partially resolves Issue #565 (it resolves the issue for deterministic vx but not ensemble vx).

Specific changes:

* Update lua module file for vx tasks to suppress "Logging error" messages in vx task log files.
* Rename experiment variable MODEL to VX_FCST_MODEL_NAME to clarify that this is the name of the forecast model in the context of verification (and which will be used in the vx output files). This requires updates to most (all?) of the * METplus configuration files and the verification ex-scripts.
* Create the new variable VX_FCST_INPUT_BASEDIR to allow the user to specify a directory in which to look for staged forecast output (instead of running a forecast).
* Modify the rocoto template xml (FV3LAM_wflow.xml) to make dependencies of vx tasks on post-processing tasks appear only when the post tasks are enabled.
* Add a new WE2E test category subdirectory named verification in which to group all vx tests (since more vx tasks will be coming in future PRs). Move the two existing tests MET_verification and MET_ensemble_verification from wflow_features to verification, and add a new test named MET_verification_only_vxto test the capability that this PR introduces.
Note: The new WE2E test MET_verification_only_vx requires new data, specifically post-processed forecast output from the SRW App. This data needs to be staged on each platform; currently, it is located in a personal directory on Hera.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant