Custom Query (116 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (79 - 81 of 116)

Ticket Resolution Summary Owner Reporter
#169 fixed Field with attribute "once" is not correctly showed in workflow graphe yushan yushan
#101 fixed __field_undef_id as name of variable with Time Series mhnguyen aclsce
Description

If no "name" attribute is specified, the name of variable used in Time Series file is "__field_undef_id" instead of the id of the variable. Example : <field id="flat" long_name="Latent heat flux" unit="W/m2" /> ... <file id="histday" timeseries="both" ts_prefix="TS_atm" >

<field field_ref="flat" level="1" />

... gives the following file : netcdf TS_atm_flat_20000101-20000131 { ...

float __field_undef_id_92(time_counter, lat, lon) ;

__field_undef_id_92:long_name = "Sensible heat flux" ; __field_undef_id_92:units = "W/m2" ; __field_undef_id_92:online_operation = "average" ; __field_undef_id_92:interval_operation = "600 s" ; __field_undef_id_92:interval_write = "1 d" ; __field_undef_id_92:cell_methods = "time: mean (interval: 600 s)" ; __field_undef_id_92:_FillValue = 9.96921e+36f ; __field_undef_id_92:missing_value = 9.96921e+36f ; __field_undef_id_92:coordinates = "time_centered" ;

....

#62 fixed Feeding a 2D global grid with processes working 1D is not working ymipsl ssenesi
Description

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

Note: See TracQuery for help on using queries.