Custom Query (116 matches)
Results (1 - 3 of 116)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#87 | worksforme | Duration arithmetics does not work | ymipsl | ssenesi |
Description |
According to the ref_guide : Arithmetic operations on durations The following arithmetic operations on durations are available: • Addition: xios_duration = xios_duration + xios_duration • Subtraction: xios_duration = xios_duration - xios_duration • Multiplication by a scalar value: xios_duration = scalar * xios_duration or xios_duration = xios_duration * scalar • Negation: xios_duration = -xios_duration But gfortran doesn't agree : CALL XIOS_SET_FIELD_ATTR(HREC, freq_op=KFREQOP*XIOS_HOUR)
Error: Operands of binary numeric operator '*' at (1) are INTEGER(4)/TYPE(xios_duration) CALL XIOS_SET_FIELD_ATTR(HREC, freq_offset=0.*XIOS_SECOND)
Error: Operands of binary numeric operator '*' at (1) are REAL(8)/TYPE(xios_duration) |
|||
#92 | worksforme | Using named constants in filters/operations | ymipsl | ssenesi |
Description |
Assume you want to convert an energy flux in mass flux using an XIOS filter :
<field id="tran" name="tran" unit="kg m-2 s-1"> evptr / 2.5008E+6</field> It would be smarter to use (and re-use) a named constant, such as in :
<variable_definition> <variable id="coeffl" type="float">2.5008E+6</variable> </variable_definition> <field_definition id="field_definition" operation="instant" prec="4"> <field id="tran" name="tran" unit="kg m-2 s-1"> evptr / coeffl </field> </field_definition> However, this does not work |
|||
#88 | duplicate | Consistency check 'ni .le. ni_glo' unrelevant for data_dim=1 and curvilinear grid | ymipsl | ssenesi |
Description |
At node/domain.cpp l693, a test read as if (ni.getValue() < 0 || ibegin.getValue() < 0 ) // || (ibegin.getValue() + ni.getValue()) > ni_glo.getValue()) ERROR("CDomain::checkLocalIDomain(void)", << "[ id = " << this->getId() << " , context = '" << CObjectFactory::GetCurrentContextId() << " ] " << "The local domain is wrongly defined," << " check the attributes 'ni_glo' (" << ni_glo.getValue() << "), 'ni' (" << ni.getValue() << ") and 'ibegin' (" << ibegin.getValue() << ")"); The third condition does not make sense in the case of data_dim=1 and grid types curvilinear and regular , as each task may handle up to ni_glo*nj_glo grid cells. |
Note: See TracQuery
for help on using queries.