Custom Query (115 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (10 - 12 of 115)

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Ticket Resolution Summary Owner Reporter
#113 fixed XIOS attribute to specify netcdf attribute "cell_methods" ymipsl aclsce
Description

For CMIP6 workflow, the user needs to specify by hand, the netcdf attribute "cell_methods", especially when the requested cell_methods attribute is not associated to a XIOS filter. For example : "area: mean where land time: mean". Examples of cell_methids required by CMIP Data Request are here : http://clipc-services.ceda.ac.uk/dreq/index/cellMethods.html

#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.

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Note: See TracQuery for help on using queries.