Custom Query (115 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1 - 3 of 115)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#26 fixed name of coordinate one-dimensional variable ymipsl aclsce
Description

As it is said in CF convention (http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/cf-conventions.html): "We use this term precisely as it is defined in section 2.3.1 of the NUG 2.3.1 of the NUG . It is a one-dimensional variable with the same name as its dimension [e.g., time(time)], and it is defined as a numeric data type with values that are ordered monotonically. Missing values are not allowed in coordinate variables."

It means we have to rename lon(x) into lon(lon) or x(x) (same for lat and time_counter). Comment : lon(lon) seems better than x(x)...

Thanks !

#27 fixed compilation of XIOS with --use_oasis option aclsce aclsce
Description

When you compile XIOS with the "--use_oasis", it is needed to have netcdf fortran interface library at the linking step. So far there is : NETCDF_LIB="-lnetcdf" in arch*.path configuration files of XIOS. "-lnetcdff" is missing to compile with "--use_oasis" option because oasis library needs it.

Proposition : add a NETCDF_LIB="-lnetcdff -lnetcdf" in make_xios file only if "$use_oasis" == "true" ?.

#28 fixed compilation XIOS Oasis path aclsce aclsce
Description

So far, the path of Oasis library is by default : OASIS_INCDIR="-I$WORKDIR/NEMO_COUPLE/prism/X64/build/lib/psmile.MPI1" OASIS_LIBDIR="-L$WORKDIR/NEMO_COUPLE/prism/X64/lib" in arch*path configuration files.

It is not very generic, in particular if we want to include XIOS compilation in IPSL coupled model compilation. We would like to have a relative path instead of absolute path.

Proposition : Replace the actual path by : OASIS_INCDIR="-I$PWD/../../prism/X64/build/lib/psmile.MPI1" OASIS_LIBDIR="-L$PWD/../../prism/X64/lib"

Thanks !

1 2 3 4 5 6 7 8 9 10 11
Note: See TracQuery for help on using queries.