Custom Query (115 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (52 - 54 of 115)

Ticket Resolution Summary Owner Reporter
#86 fixed Allowing durations expressed as strings with the Fortran API ymipsl ssenesi
Description

Model developpers would appreciate to be able to :

call xios_set_attr('field',freq_op='6h')

i.e. to benefit from the API of the same features as in xml file for expressing durations (without managing XIOS types)

I didn't find a function for converting from string to duration, which could help in this respect

#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)

1

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)

1

Error: Operands of binary numeric operator '*' at (1) are REAL(8)/TYPE(xios_duration)

#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.