Custom Query (126 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (43 - 45 of 126)

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 !

#29 fixed Need more explicit error message ymipsl omamce
Description

Error message

=> Error [CDomain::checkAttributes(void)] : In file
'/ccc/work/cont003/dsm/p86mart/CPL/CM6-03/modeles/XIOS/src/node/domain.cpp',
line 267 -> the mask has not the same size than the local domain

An information on the local domain size and the mask size would be appreciated.

#30 fixed "Once" operation attribute ymipsl aclsce
Description

When I define a field (for example "Areas" with the following attribute operation="once", it seems it is needed to do the "call xios_send_field("Areas",...)" every timestep of the model (defined thanks the call to xios_set_timestep). If I do only one call to "xios_send_field("Areas",...)", there is nothing as value of my field "Areas" in my file (only missing values)...I think it is not normal.

Thanks !

Note: See TracQuery for help on using queries.