Custom Query (116 matches)

It seems the use of "indexed_output" field attribute impacts the following fields written on the same grid.

• Example 1 :

     <file id="output" name="output" >
        <field field_ref="field_A" />
      </file>
      <file id="output_indexed" name="output_indexed" >
        <field field_ref="field_A" indexed_output="true" />
      </file>
      <file id="output_noindexed" name="output_noindexed">
           <field field_ref="field_A" />
       </file>
  

  • Results
    • field_A in output.nc file is OK
    • field_A in output_noindexed.nc is NOT OK

• Example 2 :

     <file id="output" name="output" >
        <field field_ref="field_A" />
      </file>
      <file id="output_noindexed" name="output_noindexed">
           <field field_ref="field_A" />
       </file>
      <file id="output_indexed" name="output_indexed" >
        <field field_ref="field_A" indexed_output="true" />
      </file>
  

  • Results
    • field_A in output.nc file is OK
    • field_A in output_noindexed.nc is OK

I know this may seem odd, but I tried it anyway : outputting some diags with freq_op="1ts" and split_freq="1ts" In that case, you only get the 'year' part of %start_date%

When reading an xml construct such as

<field field_ref="albs" default_value="1.e+20"/>/>

which shows a syntax error near to the end of line, Xios parser just holds

If the xml file is quite long, you may spend some tens of minutes searching for the error (assuming you suspect it is a syntax error, and you are not beginning your search elsewhere ....)