Custom Query (115 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (37 - 39 of 115)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Ticket Resolution Summary Owner Reporter
#60 fixed String variable with whitespaces are incorrectly parsed rlacroix rlacroix
Description

How to reproduce:

   <file_definition type="multiple_file" par_access="collective" output_freq="6h" output_level="10" enabled=".TRUE.">
     <file id="output" name="output"> 
        <field field_ref="field_A" />
        <variable id="my_attribute1" type="string">surf_att</variable>
        <variable id="my_attribute2" type="string">I love whitespaces</variable>
     </file>
   </file_definition>

Using this configuration file will result in the following NetCDF output:

// global attributes:
		:name = "output" ;
		:description = "Created by xios" ;
                ...
		:my_attribute1 = "surf_att" ;
		:my_attribute2 = "I" ;

Expected result would be :my_attribute2 = "I love whitespaces" ;

#62 fixed Feeding a 2D global grid with processes working 1D is not working ymipsl ssenesi
Description

Attached source test1d.90 is a modified version of test_complete.f90. It reduces nj_glo to a value of 3 (instead of 100°. Next, it defines "domain_1" as being the same global domain as "domain_A", being fed by processes which work on the same 2D sub-domains as for domain_A, except that they declare themselves to Xios as being 1D sub-domains, and they provide i_index and j_index for describing the mapping of the 1D local data to the 2D global domain.

Execution results in incorrect data in field_1 (which actually receive, at some location, values from field_A at llm=3) . This may be due to misunderstanding in the API arguments in this configuration

iodef.xml and result file are also attached

#63 invalid Complementing field definition by sourcing from an alternate file does not work ymipsl ssenesi
Description

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)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Note: See TracQuery for help on using queries.