Custom Query (116 matches)
Results (34 - 36 of 116)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #41 | fixed | Do not take missing value for averaging operation | ymipsl | ymipsl |
| Description |
When you have some missing data in the model, it would be convenient to avoid to take into acount these values when temporal operation like averaging are performed. |
|||
| #42 | fixed | Add the possibility to add user defined global and field attributes into a netcdf file | ymipsl | smasson |
| #44 | fixed | problem with xios_field_is_activate | ymipsl | jgipsl |
| Description |
Concerning XIOS rev 477 The problem is described in the following exemple in ORCHIDEE : IF (xios_field_is_active("RootMoist") .OR. xios_field_is_active("DelSoilMoist") .OR. &
xios_field_is_active("DelIntercept") .OR. xios_field_is_active("DelSWE") .OR. &
xios_field_is_active("SoilWet")) THEN
almaoutput=.TRUE.
WRITE(numout,*) 'almaoutput has been set to true in xios_orchidee_init'
END IF
Case 1) Everything is fine when these variables are declared only in field_def_orchidee.xml. almaoutput becomes FALSE. See exemple at curie : /ccc/scratch/cont003/dsm/p86ghatt/LMDZOR/XIOS/RUNDIR/TESTING/RUN_rev1960/prod_mpi_omp/TestAlma Case 2) If one or several of these variables are set in file_def_orchidee.xml but the file is deactivated, the result is almaoutput=TRUE. This is not ok. See here an extract from file_def_orchidee.xml : <file id="sechiba2" name="sechiba_out_2_xios" output_level="10" output_freq="1d" enabled=".FALSE."> <field field_ref="RootMoist" level="1"/> <field field_ref="Areas" level="1"/> Exemple : /ccc/scratch/cont003/dsm/p86ghatt/LMDZOR/XIOS/RUNDIR/TESTING/RUN_rev1960/prod_mpi_omp/TestAlma2 I think the behaviour of xios_field_is_activate was correct in earlier versions of XIOS. |
|||
