Custom Query (116 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (28 - 30 of 116)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Ticket Resolution Summary Owner Reporter
#151 invalid Declaring with same ID does not raise an error ymipsl omamce
Description

I you declare in your XML something like :

 <file id="file1" name_suffix="_grid_T"

An then later in the XML :

 <file id="file1" name_suffix="_grid_U"

Only the lastest declared file is created. XIOS does not see that an ID is used several times, and does not raise any error or warning.

The same problem exists for ID in variable declarations, and probably for other objects.

It might be very hard for the user to understand that his/her file or variable is not written.

XIOS should see the conflict and raise an error (at least a warning).

Thanks,

Olivier

#60 fixed String variable with whitespaces are incorrectly parsed rlacroix rlacroix
Description

How to reproduce:

   <file_definition type="multiple_file" par_access="collective" output_freq="6h" output_level="10" enabled=".TRUE.">
     <file id="output" name="output"> 
        <field field_ref="field_A" />
        <variable id="my_attribute1" type="string">surf_att</variable>
        <variable id="my_attribute2" type="string">I love whitespaces</variable>
     </file>
   </file_definition>

Using this configuration file will result in the following NetCDF output:

// global attributes:
		:name = "output" ;
		:description = "Created by xios" ;
                ...
		:my_attribute1 = "surf_att" ;
		:my_attribute2 = "I" ;

Expected result would be :my_attribute2 = "I love whitespaces" ;

#65 fixed Regression caused by automatic detection of buffer size mhnguyen rlacroix
Description

As far as I can tell the automatic detection of buffer size is causing two issues (closely related):

  • XIOS will raise an error if a context has no enabled output file which it has no good reasons to do.
  • XIOS can fail if internal messages are bigger than the estimated output data.

This can probably be solved by always allocating a buffer with a fixed minimum size we know will always be sufficient to allocate the internal messages.

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