| Version 52 (modified by flavoni, 14 years ago) (diff) |
|---|
Integrating IOM_PUT
Integrating IOM_PUT
Working tests:
- test with iom_put (compiled with key_iomput):
/work/cont003/flavoni/LIBIGCM_NEMO/LIKE-COUPLED/test_iom_lib14_rev1661_WR/modipsl/config/ORCA2_LIM/IGCM_lim14_io
KO: at the beginning : **** 90 Fatal exception PROG=mod_event_client.event__set_time ELN=164(4002dc900)
- same test but without iom_put (in opa9.card io_xml=n):
/work/cont003/flavoni/LIBIGCM_NEMO/LIKE-COUPLED/test_lib14_rev1661_WR/modipsl/config/ORCA2_LIM/IGCM_lim14
OK. Look at atlas and monitoring: http://dods.extra.cea.fr/data/flavoni/ORCA2_LIM2/lib14if
27/11/2009: downloading NEMO_DEV you have iomput by default (tag v3_2)
By default iom_put is activated
- key_iomput in modipsl/config/ORCA2_LIM/scripts/BB_make.ldef
- namelist in IGCM00 is the same that namelist in EXP00 (nothing to change if you want to use iodef.xml by default, like an example)
- iodef.xml in IGCM00 is the same that namelist in EXP00 (nothing to change if you want to use iodef.xml by default, like an example)
- To have post traitement different by default you need to create POST directory in IGCM00
Create POST directory under $SUBMIT_DIR:
In POST directrory you can put:
monitoring01_lim2_ORCA2.cfg
monitoring01_opa9_ORCA2.cfg
(In monitoring01_lim2_ORCA2.cfg I removed ileadfra because now this variable does not exists) see https://forge.ipsl.jussieu.fr/nemo/wiki/private/libIGCM/postprocessingpage
At this point: open problems:
- In ~commonaccount/atlas/monitoring01_opa9_ORCA2.cfg there are only 8 variables so we can do monitoring of this ones (if you want differents you have to add variables in opa9.card and coeherntly create POST directory under IGCM00 and put it a corresponding monitoring01_opa9_ORCA2.cfg) to work today with iodef.xml example and monitoring01_opa9_ORCA2.cfg common account you have to leave in opa9.card only section like this:
- Don't have ATLAS for "ice cover": because new variable is named soicecov and in atlas is written ileadfra
