Custom Query (115 matches)


Show under each result:

Results (67 - 69 of 115)

Ticket Resolution Summary Owner Reporter
#63 invalid Complementing field definition by sourcing from an alternate file does not work ymipsl ssenesi

When wanting to add some field definition by sourcing an alternate file, you should be able to write :

<field_definition> <field id="default_field"domain_ref="FULL"></field_definition> <field_definition id="field_definition" src="./surfex_base.xml" />

where the content of surfex_base.xml is e.g. : <field_definition > <field id="LE" name="leprime" /> </field_definition>

This crashes XIOS with "MPI_ERR_COMM: invalid communicator" (while putting the equivalent content at the same place in the master xml file works fine)

#64 fixed Compile error when using option netcdf4_internal on Bull Intel with mpiifort ymipsl ssenesi

In that case, with release 549, I get a 'catastrophic error' (I didn't choose that qualifier myself !) :

fcm_internal compile:C netcdf /home/gmgec/mrgu/senesis/SAVE/XIOS_mt_par/extern/netcdf4/mmapio.c mmapio.o 1 mpiicc -o mmapio.o -DUSING_NETCDF_PAR -DUSING_NETCDF_INTERNAL -I/home/gmgec/mrgu/senesis/SAVE/XIOS_mt_par/inc -ansi -diag-disable 1125 -diag-disable 279 -openmp -openmp-threadprivate compat -openmp-report2 -O3 -D BOOST_DISABLE_ASSERTS -I/home/gmgec/mrgu/senesis/SAVE/XIOS_mt_par/extern/netcdf4 -I/opt/softs/libraries/ICC13.1.4.183/hdf5-1.8.11_par/include -I/home/gmgec/mrgu/senesis/SAVE/XIOS_mt_par/extern/src_netcdf -I/home/gmgec/mrgu/senesis/SAVE/XIOS_mt_par/extern/boost/include -I/home/gmgec/mrgu/senesis/SAVE/XIOS_mt_par/extern/rapidxml/include -I/home/gmgec/mrgu/senesis/SAVE/XIOS_mt_par/extern/blitz/include -c /home/gmgec/mrgu/senesis/SAVE/XIOS_mt_par/extern/netcdf4/mmapio.c /home/gmgec/mrgu/senesis/SAVE/XIOS_mt_par/extern/netcdf4/mmapio.c(38): catastrophic error: #error directive: mmap not fully implemented: missing MAP_ANONYMOUS

#error mmap not fully implemented: missing MAP_ANONYMOUS

#70 fixed Flexibility and verbosity of parse_xml ymipsl omamce

2 requests

  • When parse_xml is successful, it returns nothing. Could be a bit puzzling. A message would be appreciated.
  • parse_xml does not take any parameter. The possibility to run something like parse_xml PARAM/iodef.xml would be helpful. In this case, parse_xml should assume that other xml files (included) are in the same directory.



Note: See TracQuery for help on using queries.