Custom Query (116 matches)

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

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" ;

If a an output_freq of "2h" is set, my model having a timestep of 3h, XIOS does crash with FPE. Increasing output_freq to 3h 'solves' the problem. A smoother , landing with an an explicit explanantion would be friendlier.