Custom Query (116 matches)

So far if multiple axes are defined (e.g. axis1, axis2, etc.), but only one is used (e.g.all output fields in file are with axis_ref="axis2"), then it is the only axis written to the file.

Allowing users to specify that alternative axes, although not used, should be included in the output file would be useful.

Maybe by adding a flag output="always" to the axis (or file?) parameters?

In date.cpp, the function

void CDate::addMonth(int value) { Value doit être égale à 1 ou -1.

this->month += value; if (this->month == 13) { year++; this->month = 1; } if (this->month == 0) { year--; this->month = 12; }

}

Assumes that there are 12 months/year, which is not the case for a "user_defined" calendar. A more generic version could be:

void CDate::addMonth(int value) { Value doit être égale à 1 ou -1.

const CCalendar& c = getRelCalendar(); int nbMonth = c.getYearLength() ;

this->month += value; if (this->month == nbMonth+1) { year++; this->month = 1; } if (this->month == 0) { year--; this->month = nbMonth; }

}

XIOS is able to read weights from a file then use them to do interpolation of a domain to another. There are cases in which these weights should be computed once then reused over and over. Therefore, XIOS should be able to write weights into file. Some specifications for this:

• Flag for interpolation_domain

+) filename: Already exists +) weights="read/write"

• Behaviors:

+) weights="write" -> write weights into file. If there is no filename -> default filename weights.nc will be used, otherwise use filename. Filename will be always overwritten in this case. +) weights="read" -> try to read weights from a file. If there is no filename-> default filename weights.nc will be used, otherwise use filename. If there is no file to read at all-> switch to write mode.