Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
noresm:runmodel:advancednoresm2 [2014-01-27 13:24:14] alfg created |
noresm:runmodel:advancednoresm2 [2022-05-31 09:29:32] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Advanced configuration of NorESM2 ===== | + | ====== Advanced configuration of NorESM2 ====== |
+ | |||
+ | **NOTE THAT THE COMPSETS MENTIONED IN THIS EXAMPLE ARE NO LONGER MAINTAINED! THE GENERAL EXPLANATION AND IDEAS ARE STILL VALID! | ||
+ | ** | ||
+ | ===== Creating a new compset ===== | ||
+ | |||
+ | The essential file to edit is | ||
+ | < | ||
+ | ~/ | ||
+ | </ | ||
+ | |||
+ | This examples shows how to simply add a to the " | ||
+ | |||
+ | Under "< | ||
+ | |||
+ | < | ||
+ | <COMPSET sname=" | ||
+ | </ | ||
+ | |||
+ | The " | ||
+ | |||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | The compset needs a description, | ||
+ | < | ||
+ | <desc compset=" | ||
+ | </ | ||
+ | |||
+ | We could also define a specific use-case (namelist) for our compset. This would need a line like: | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | This would only work if the file my_namelist.xml exists as | ||
+ | < | ||
+ | noresm/ | ||
+ | </ | ||
+ | |||
+ | |||
+ | ===== Setting up a case with the new compset and building the model ===== | ||
+ | |||
+ | It should now be possible to create a new case directory, which we here name FAMIPOSLOtst | ||
+ | and configure with 1 degree horizontal atmospheric resolution; | ||
+ | |||
+ | < | ||
+ | ./ | ||
+ | </ | ||
+ | |||
+ | and finally set up and compile the model: | ||
+ | < | ||
+ | cd ../ | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | ./ | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | ./ | ||
+ | </ | ||
+ | |||
+ | ===== Why does it work to change config_compsets.xml ? | ||
+ | |||
+ | In NorESM there are 3 new config-options for CAM: | ||
+ | * -cam-oslo aerlife (turns on transport of oslo tracers) | ||
+ | * -cam-oslo dirind | ||
+ | * -cam-oslo warmclouds (also turns on interaction with warm clouds) | ||
+ | |||
+ | They change number of tracers and turn on different preprocessor flags in in a perl script called " | ||
+ | < | ||
+ | models/ | ||
+ | </ | ||
+ | |||
+ | To understand the implementation do: | ||
+ | < | ||
+ | svn diff -r 202 models/ | ||
+ | </ | ||
+ | |||
+ | The new oslo-options also need to be defined, see | ||
+ | < | ||
+ | models/ | ||
+ | </ | ||
+ | |||
+ | To see how these new options were added, do: | ||
+ | < | ||
+ | svn diff -r 202 models/ | ||
+ | </ | ||
+ | |||
+ | |||
+ | ===== Configure nudging ===== | ||
+ | |||
+ | ==== Create the met-data ==== | ||
+ | |||
+ | First run the model to produce 6 hourly data. The following namelists are needed: | ||
+ | |||
+ | < | ||
+ | user_nl_cam | ||
+ | & | ||
+ | mfilt = 1, 4, | ||
+ | nhtfrq | ||
+ | avgflag_pertape =' | ||
+ | fincl2 | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | user_nl_clm | ||
+ | & | ||
+ | hist_mfilt | ||
+ | hist_nhtfrq | ||
+ | hist_avgflag_pertape | ||
+ | hist_fincl2 | ||
+ | </ | ||
+ | |||
+ | ==== Use the met-data in another run ==== | ||
+ | |||
+ | First create a compset which has the configure-option " | ||
+ | |||
+ | Then use this compset to create a case. You need the following user-input (for example in your user_nl_cam) | ||
+ | |||
+ | < | ||
+ | & | ||
+ | met_data_file='/ | ||
+ | met_filenames_list = '/ | ||
+ | </ | ||
+ | |||
+ | This info can be added directly in a use_case which you associate with the compset created (see e.g. 2000_cam5_oslonudge.xml) | ||
+ | |||
+ | where met_data_file is the first met-data file to read, and met_filenames_list is a list of the following met-data. The first lines of the file should look something like this (guess what the rest of the file should look like? 8-o: ) | ||
+ | < | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | </ | ||
+ | |||
+ | This file can be created at the place where you put the metdata with this command: | ||
+ | < | ||
+ | alfgr@hexagon-4:/ | ||
+ | </ | ||
+ | |||
+ | ==== Namelist options ==== | ||
+ | When looking at aerosol indirect effects, it's recommended to nudge only U, V and PS: | ||
+ | < | ||
+ | & | ||
+ | | ||
+ | </ | ||
+ | |||
+ | Choose relaxation time (hours). Use the same time as dt in met_data_file: | ||
+ | < | ||
+ | & | ||
+ | | ||
+ | </ | ||
+ | |||
+ | |||
+ | ==== Nudge to ERA-interim reanalysis ==== | ||
+ | Link to ERA-interim metdata instead of model produced metdata. Remember to choose the files corresponding to your resolution (examples below are for f09_f09 and 32 levels in the vertical): | ||
+ | < | ||
+ | & | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | Add also the ERA-topography (no matter which fields you are nudging): | ||
+ | < | ||
+ | & | ||
+ | | ||
+ | </ |