Skilled (#3) - [key_floats] Problem with NFLOAT in IOM.F90 (#41) - Message List

[key_floats] Problem with NFLOAT in IOM.F90

Hi I am using the stable NEMO version 3.6 with XIOS2 and compiling with:

makenemo -m GBAR -j1 -v3 -r GYRE -n GYRE_float add_key "key_iomput key_xios2 key_floats"

I get the following error at compilation time :

mpiifort -c -cpp -o iom.o -I/zhome/c1/e/39819/workspace/tmp/NEMOGCM/CONFIG/GYRE_float/BLD/inc -i4 -r8 -O3 -fp-model precise -I/zhome/c1/e/39819/workspace/xios-2.0/inc
-I/appl/netcdf-par/ -I/appl/netcdf-fortran-par/4.4.4/intel-2017update4-sl64-intelmpi/include
-c /zhome/c1/e/39819/workspace/tmp/NEMOGCM/CONFIG/GYRE_float/BLD/ppsrc/nemo/iom.f90
/zhome/c1/e/39819/workspace/tmp/NEMOGCM/CONFIG/GYRE_float/BLD/ppsrc/nemo/iom.f90(196): error #6512: A scalar-valued expression is required in this context.   [NFLOAT]
      CALL iom_set_axis_attr( "nfloat", (/ (REAL(ji,wp), ji=1,nfloat) /) )

The compiler is INTEL ifort (IFORT) 17.0.4 20170411

To me looks like a syntax error as nfloat is a vector, and indeed I wold expect to have a scalar in that loop, i.e. jpnfl which is the particle numbers.

  • Message #68

    Thanks Patrizio for reporting it.

    The variable for the floats number has changed at some point but the iom routine was not modified accordingly.
    It has been fixed with r9429

    • Message #74

      Thanks. Indeed, this solves the compilation error but it still has a runtime error in using XIOS:

      Error [void CGrid::inputField(const  CArray<double,n>& field, CArray<double,1>& stored) const] :
      In file '/zhome/c1/e/39819/workspace/xios-2.0/inc/grid.hpp', line 307 -> [ Awaiting data of size = 1408, Received data size = 2 ]
      The data array does not have the right size! Grid = __grid_1point_nfloat__

      This is generated at the first call to iom_put in flowri.F90. Note that "Received data size = 2" is likely due to "jpnfl = 2" in namelist_cfg

      I can't really figure out if the problem is with NEMO or XIOS2, but can see that both file_def.xml and field_def.xml are reasonably setted.


No attachments created.