New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
user/flavoni/libIGCM/common_account – NEMO
wiki:user/flavoni/libIGCM/common_account

Version 10 (modified by flavoni, 15 years ago) (diff)

--

Boundary conditions and common account


Using common account to store boundary conditions

First of all see IPSL's documentation :

http://wiki.ipsl.jussieu.fr/wiki_ipsl/EsciComptes

We use common account to put boundary conditions for reference configuration ORCA2_LIM.
Common account are one at CCRt and one at IDRIS

at CCRT

mercure: in ~comptecommun/dmf/IGCM/BC/OCE/
we put all configurations:
ORCA2_LIM2
ORCA2_LIM2_PISCES
IPSLCM5
IPSLCM4_v1
IPSLCM4_v1_OASIS3
IPSLCM4_v2
IPSL_ESM_V1

that are links to

~commonaccount/dmf/IGCM/STORAGE/BC/OCE/NEMO/ORCA2_TEST/ORCA2_LIM2
~commonaccount/dmf/IGCM/STORAGE/BC/OCE/NEMO/ORCA2_TEST/ORCA2_LIM2_PISCES
~commonaccount/dmf/IGCM/STORAGE/BC/OCE/NEMO/ORCA2_TEST/IPSLCM5
etc...

NOTE : In this moment it is ORCA2-TEST because we're waiting for test of IPSLCM5, then it will became ORCA2

And in every configuration's directory in STORAGE we put boundary condition's files.
For ORCA2_LIM2 they are divided by nemo tags version's name, in which we put tar file for Boundary Conditions, and all files from tar xvf file.tar :
tree ~comptecommun/dmf/IGCM/STORAGE/BC/OCE/NEMO/ORCA2_TEST/ORCA2_LIM2 :

v3
|ORCA2_LIM_nemo_v3.tar
|1_bathy_level.nc
|1_bathy_meter.nc
|1_coordinates.nc
|1_data_1m_potential_temperature_nomask.nc
|1_data_1m_salinity_nomask.nc
|1_flx.nc
|1_geothermal_heating.nc
|1_taux_1m.nc
|1_tauy_1m.nc
|EMPave_old.dat
|ahmcoef
|bathy_level.nc
|bathy_meter.nc
|bathy_updated.nc
|coordinates.nc
|data_1m_potential_temperature_nomask.nc
|data_1m_salinity_nomask.nc
|flx.nc
|geothermal_heating.nc
|runoff_1m_nomask.nc
|sss_data.nc
|sst_data.nc
|taux_1m.nc
|tauy_1m.nc
v3_1 ORCA2_LIM_nemo_v3.1.tar
1_bathy_level.nc
1_bathy_meter.nc
1_coordinates.nc
1_data_1m_potential_temperature_nomask.nc
1_data_1m_salinity_nomask.nc
1_flx.nc
1_geothermal_heating.nc
1_taux_1m.nc
1_tauy_1m.nc
EMPave_old.dat
ahmcoef
bathy_level.nc
bathy_meter.nc
bathy_updated.nc
coordinates.nc
data_1m_potential_temperature_nomask.nc
data_1m_salinity_nomask.nc
flx.nc
geothermal_heating.nc
runoff_1m_nomask.nc
sss_data.nc
sst_data.nc
subbasins.nc
taux_1m.nc
tauy_1m.nc

at IDRIS

ulam or rhodes : in ~comptecommun/IGCM/BC/OCE/
we put all configurations:
ORCA2_LIM2
ORCA2_LIM2_PISCES
IPSLCM5
IPSLCM4_v1
IPSLCM4_v1_OASIS3
IPSLCM4_v2
IPSL_ESM_V1

that are links to

~commonaccount/IGCM/STORAGE/BC/OCE/NEMO/ORCA2_TEST/ORCA2_LIM2
~commonaccount/IGCM/STORAGE/BC/OCE/NEMO/ORCA2_TEST/ORCA2_LIM2_PISCES
~commonaccount/IGCM/STORAGE/BC/OCE/NEMO/ORCA2_TEST/IPSLCM5

and all like at CCRT

How to add new configuration

If we want to add new configuration in common account we have to :

  1. create a new Tag_Name in config.card file.
  2. create resolution_name directory ( for example ORCA2.5 ) in common account STORAGE/BC/OCE/NEMO directory
  3. in this last directory create configuration_reference_name directory ( for example ORCA2.5_LIM2, ORCA2.5_LIM2_PISCES )
  4. in this last directory create other sub-directory for every boundary condition data version

NOTE: that to have atlas and monitoring for new configurations it is important also :

  1. to create in common account in atlas directory new monitoring01_component_name_resolution_name.cfg
  1. to add in libIGCM/AA_create_se new configuration's name