If you meet all the [requirements](mar-forecast-intro) to set up a MAR-based weather forecast, follow the next steps carefully to first set up a folder hierarchy that will act as the backbone of the forecast.
If you meet all the [requirements](mar-forecast-intro) to set up a MAR-based weather forecast, follow the next steps carefully to first set up a folder hierarchy that will act as the backbone of the forecast. This hierarchy will indeed provide all the base components of the so-called **operational chain**, i.e., the sequence of practical operations that are run to prepare and run MAR forced by [ERA5T](https://forum.ecmwf.int/t/release-of-era5t/1136) or [GFS](https://en.wikipedia.org/wiki/Global_Forecast_System) one day at a time, the latter corresponding to an actual weather forecast.
1. On your target computer (i.e. where the forecast will run), e.g. a cluster, create a new directory at a suitable location to store the software and main resources of the operational forecast chain. **This directory must be permanent** as it will both contain the main software, the `MARsim` archives used for the forecast as well as logs written by various parts of the operational chain. This directory will be subsequently refered to as `$DIR`.
1. On your target computer (i.e. where the forecast will run), e.g. a cluster, create a new directory at a suitable location to store the software and main resources of the operational forecast chain. **This directory must be permanent** as it will both contain the main software, the `MARsim` archives used for the forecast as well as logs written by various parts of the operational chain. This directory will be subsequently refered to as `$DIR`.
...
@@ -17,7 +17,7 @@ If you meet all the [requirements](mar-forecast-intro) to set up a MAR-based wea
...
@@ -17,7 +17,7 @@ If you meet all the [requirements](mar-forecast-intro) to set up a MAR-based wea
7. In `mar-src`, copy the executable of your MAR simulation and create a symbolic link to it named `MAR.exe`. You can also copy your executable in a separate directory or even rename the executable (instead of using a symbolic link); what matters the most is the `MAR.exe` name can be used to run your MAR executable.
7. In `mar-src`, copy the executable of your MAR simulation and create a symbolic link to it named `MAR.exe`. You can also copy your executable in a separate directory or even rename the executable (instead of using a symbolic link); what matters the most is the `MAR.exe` name can be used to run your MAR executable.
8. Still in `mar-src`, copy all the files that are normally present in a MAR working directory at start, with the exception of lateral boundary forcings (which will come from the `MARsim` archives). This includes the typical contents of `~/MAR/src/datMAR` and from `~/MAR/usr`, and in particular `ICEvou.dat` (to tune your output variables).
8. Still in `mar-src`, copy all the files that are normally present in a MAR work directory at start, with the exception of lateral boundary forcings (which will come from the `MARsim` archives). This includes the typical contents of `~/MAR/src/datMAR` and from `~/MAR/usr`, and in particular `ICEvou.dat` (to tune your output variables).
9. Still in `mar-src`, add your (uncompressed) `MARdom_DOM*.dat` file (normally found compressed in `~/MAR/sim/DOM/input/MARdom/EXP` where `DOM` is your domain and `EXP` your simulation) and create a symbolic link to it named `MARdom.dat`.
9. Still in `mar-src`, add your (uncompressed) `MARdom_DOM*.dat` file (normally found compressed in `~/MAR/sim/DOM/input/MARdom/EXP` where `DOM` is your domain and `EXP` your simulation) and create a symbolic link to it named `MARdom.dat`.
...
@@ -27,4 +27,4 @@ If you meet all the [requirements](mar-forecast-intro) to set up a MAR-based wea
...
@@ -27,4 +27,4 @@ If you meet all the [requirements](mar-forecast-intro) to set up a MAR-based wea
12. Finally, review carefully and edit the `bin/region.bash` file. This file centralizes environment variables used by the forecast operational chain, such that you will not have to review and edit each script yourself to tune it for your area of interest. In particular, you have to give the dimensions of your MAR grid and the target coordinates ranges of the forcings pre-processed for NESTOR. The `bin/region.bash` file also lets you decide whether or not you need to build atmospheric forcings for the NEMO model from the MAR outputs.
12. Finally, review carefully and edit the `bin/region.bash` file. This file centralizes environment variables used by the forecast operational chain, such that you will not have to review and edit each script yourself to tune it for your area of interest. In particular, you have to give the dimensions of your MAR grid and the target coordinates ranges of the forcings pre-processed for NESTOR. The `bin/region.bash` file also lets you decide whether or not you need to build atmospheric forcings for the NEMO model from the MAR outputs.
If you are done with this tutorial, you can move on with [making your MAR simulation catch up with the present](mar-forecast-era5t) thanks to ERA5T data.
If you are done with this tutorial, you can move on with [making your MAR simulation catch up with the present](mar-forecast-era5t) by forcing it with [ERA5T](https://forum.ecmwf.int/t/release-of-era5t/1136) data.
