Custom Query (116 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (52 - 54 of 116)

Ticket Resolution Summary Owner Reporter
#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.

#89 invalid Error in node/domain.cpp on ChecKDomainData ymipsl ssenesi
Description

It reads on line 792 as

      if (data_ni.isEmpty())
      {
        data_ni.setValue((data_dim == 1) ? (ni.getValue() * nj.getValue()) : ni.getValue());
      }

which is obviously wrong (set values should be reversed). This actually causes segmentation violation when nj is not set and data_dim==1; and this should lead to underestimated allocation when data_dim==2

#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

Note: See TracQuery for help on using queries.