Custom Query (116 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (88 - 90 of 116)

Ticket Resolution Summary Owner Reporter
#115 fixed Date parsing does not support whitespace rlacroix ssenesi
Description

I got an error with r1028 when writing

start_date="1950-01-01 00:00:00 + 3d + 3d "

instead of

start_date="1950-01-01 00:00:00 +3d+3d"

#125 fixed Impact of "indexed_output" on fields on the same grid rlacroix aclsce
Description

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
#127 fixed Pb with index with indexed_output on 3D fields rlacroix aclsce
Description

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.

Note: See TracQuery for help on using queries.