In the '
model' directory (i.e.,
.../polair/code/model) the user finds the directories containing each submodel. Two directories are permanent, namely the
coupler and the
parallel, as they are used in every model run scenario. However, the code in the other directories may be or may not be used in a model run, depending on the setting of certain environmental variables.
If a submodel is called into use, for example, assume that the appropriate ocean environmental variable has been activated, then precisely which ocean model a user receives depends on the status of a symbolic link in the
model directory. These symbolic links are created at runtime based on the user's
P_*_FLAVOR environment variables which are set in
.../polair/cshrc/.cshrc_polair_user initialization script and will be sourced at login if set up properly. To access, for example, the MICOM ocean model the symbolic link needs to have been assigned as
ln -fs ocean_micom ocean, which serves to connect the symbolic submodel directory
ocean to the physically existing submodel directory
ocean_micom. The same reasoning applies to the user's choice of all other submodels. A screen snapshot showing the default setup of symbolic links (once the model has been run) is given here.
To change the flavor of a submodel, it is recommended that the user edits the
.../polair/cshrc/.cshrc_polair_user file to contain the desired flavors and re-source
~/.cshrc in all open windows. New links will be created at runtime. Either run the model or update the links in the
model directory by hand (for example: delete the existing link
rm ocean and create a new link
ln -fs ocean_eulag ocean.
© David Holland.
All Rights Reserved.
If you would like further information
concerning any of the above topics
please send email .