Fortuna 2.5 Single Column Model: Difference between revisions
| (2 intermediate revisions by the same user not shown) | |||
| Line 27: | Line 27: | ||
Create your own directory and | Create your own run directory, then modify and uncomment the first executable line of <code>scm_setup</code>, which assigns <code>ESMADIR</code> to your local Fortuna 2.5 build that you are using for the SCM (you may already have this set as an environment variable). Uncomment one of the lines that assign the variable <code>CASEDIR</code> to choose the experiment to run. Then run the script from the run directory you have created. It will copy all of the necessary resource, forcing and data files to the working directory. Each experiment requires its own directory. If you modify the resource files (e.g., HISTORY.rc) you may want to copy the setup directory to your own area and modify it and the setup script accordingly so that you don't clobber your modifications. | ||
Then you can just run the model executable from the command line in the directory you created. You will have to load the proper modules by sourcing <code>src/g5_modules</code>. Although it runs with a single processor, on discover you should run it from an interactive job on a compute node (as opposed to the '''discover''' front end). This can be done by running <code>qsub -I ijob</code>, where <code>ijob</code> is the job script that sets up the environment (examples are in <code>~aeichman</code> or <code>~amolod</code>). Once the job starts it starts an interactive shell on the job node, from which you can run the GEOS-5 executable. Since all of the necessary configuration files are copied to the experiment directory, it requires none of the extra environmental infrastructure needed for a global experiment that the run script <code>gcm_run.j</code> creates. | Then you can just run the model executable from the command line in the directory you created. You will have to load the proper modules by sourcing <code>src/g5_modules</code>. Although it runs with a single processor, on '''discover''' you should run it from an interactive job on a compute node (as opposed to the '''discover''' front end). This can be done by running <code>qsub -I ijob</code>, where <code>ijob</code> is the job script that sets up the environment (examples are in <code>~aeichman</code> or <code>~amolod</code>). Once the job starts it starts an interactive shell on the job node, from which you can run the GEOS-5 executable. Since all of the necessary configuration files are copied to the experiment directory, it requires none of the extra environmental infrastructure needed for a global experiment that the run script <code>gcm_run.j</code> creates. | ||
== Creating Driving Datasets from MERRA == | == Creating Driving Datasets from MERRA == | ||
| Line 65: | Line 65: | ||
Now the ASCII .dat file used for the driving data can be created. | Now the ASCII .dat file used for the driving data can be created. | ||
Under the directory <code>src/GMAO_Shared/GEOS_Util/post</code> in your Fortuna build, apply the following CVS command: | |||
cvs | cvs upd -r b_afe_Fortuna_merra2scm merra2scm.F GNUmakefile | ||
This will check out the source file <code>merra2scm.F</code>; it must be modified to the time and location of the data set to be created. Change the parameters <code>begdate</code> and <code>enddate</code> to the dates you want to cover, but leave <code>begtime</code> and <code>endtime</code> alone. If you are replicating an existing experiment, <code>begdate</code> and <code>enddate</code> can be obtained from that experiment's <code>cap_restart</code> and <code>CAP.rc</code>, respectively. The parameters <code>lonbegin</code>, <code>lonend</code>, <code>latbegin</code>, and <code>latend</code> specify the location and appropriate values can be gleaned from the filenames in the appropriate experiment under <code>/discover/nobackup/aeichman/scm/scminfiles/</code> -- for example, the filename | |||
<code>tile.data_simple1_XY1x1-C_34N_100W_38N_95W</code>. (Note that these file names are truncated when copied by the SCM setup script.) Finally, change the variable <code>dirname</code> to the directory where you copied the MERRA data. | <code>tile.data_simple1_XY1x1-C_34N_100W_38N_95W</code>. (Note that these file names are truncated when copied by the SCM setup script.) Finally, change the variable <code>dirname</code> to the directory where you copied the MERRA data. | ||
| Line 155: | Line 155: | ||
<pre> | <pre> | ||
>> format shortG | |||
>> load FV_144x91_DC_360x180_DE.til | >> load FV_144x91_DC_360x180_DE.til | ||
>> tilelines=find(int8(FV_144x91_DC_360x180_DE(:,4))== | >> lat=40;lon=-77; | ||
>> tilelines=find(int8(FV_144x91_DC_360x180_DE(:,4))==lat & int8(FV_144x91_DC_360x180_DE(:,3))==lon );FV_144x91_DC_360x180_DE(tilelines,[1 4 3 12]) | |||
ans = | ans = | ||
100 39. | 100 39.963 -76.626 6894 | ||
100 | 100 39.96 -76.975 6895 | ||
100 | 100 40.182 -76.625 6896 | ||
100 | 100 40.187 -76.899 6899 | ||
100 | 100 40.134 -77.357 6900 | ||
100 40.353 -77.128 6901 | |||
100 39.595 -77.256 6935 | |||
19 39.566 -76.569 67187 | |||
>> | >> | ||
</pre> | </pre> | ||