Custom Query (116 matches)


Show under each result:

Results (76 - 78 of 116)

Ticket Resolution Summary Owner Reporter
#89 invalid Error in node/domain.cpp on ChecKDomainData ymipsl ssenesi

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

#90 fixed MPI dead lock in XIOS ymipsl mcastril

We are experiencing a repetitive issue with XIOS 1.0 . It appeared using NEMO 3.6 stable and more than 2600 cores, and it seemed to be solved when using Intel 16 compiler and IMPI 5. However, after updating to NEMO 3.6 current stable, the problem appears when using 1920 or more cores. I don't really get how the NEMO revision change could affect to this, but there it is.

The problem is just in this line of client.cpp:

MPI_Send(buff,buffer.count(),MPI_CHAR,serverLeader,1,CXios::globalComm) ;

In the meanwhile the server.cpp is doing MPI_Iprobe continuosly in order to receive all the MPI_Send.

What we have observed is that using a high number of cores, around 80-100 of these cores get stucked at the MPI_Send, causing the run to hang and not complete. The fact that with a certain number of cores the issue appears 80% of the times but not always, made us think that could be related with the IMPI implementation.

#92 worksforme Using named constants in filters/operations ymipsl ssenesi

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 id="coeffl"  type="float">2.5008E+6</variable>

    <field_definition id="field_definition" operation="instant" prec="4">
        <field id="tran"    name="tran"  unit="kg m-2 s-1"> evptr / coeffl </field>

However, this does not work

Note: See TracQuery for help on using queries.