Custom Query (116 matches)

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%

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

Indices of points of compressed 3D fields by using "indexed_output" field attribute are not correct :

int grid_T_moor_3D_points(grid_T_moor_3D_points) ;

grid_T_moor_3D_points:compress = "deptht y x" ;

grid_T_moor_3D_points = 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14,

These values are not correct. Note that indices are correct with 2D fields.