Custom Query (124 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:

Results (76 - 78 of 124)

← 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 →
Ticket Resolution Summary Owner Reporter
#43 wontfix Having the possibility of enforcing the addition of a axis to a file ymipsl millour
Description

So far if multiple axes are defined (e.g. axis1, axis2, etc.), but only one is used (e.g.all output fields in file are with axis_ref="axis2"), then it is the only axis written to the file.

Allowing users to specify that alternative axes, although not used, should be included in the output file would be useful.

Maybe by adding a flag output="always" to the axis (or file?) parameters?

#189 fixed Hangs when attempting to use pools and services with XIOS3 generic_testcase ymipsl acc
Description

A first attempt to use the new pools and service with XIOS3 (trunk) results in a deadlock which hangs until the job times out. This is reproducible with minimal changes to the generic_testcase example.

Changes are based on the example given in: https://forge.ipsl.jussieu.fr/ioserver/raw-attachment/wiki/WikiStart/Coupling%20workshop-CW2023.pdf

which is still the closest material that I can find to any documentation on the new concepts.

Based on XIOS3 trunk@2540 with these changes:

  • context_atm.xml 

    [generic_testcase]$ svn diff
     
    11<!-- --> 
    2 <context id="atm"> 
     2<context id="atm" default_pool_gatherer="pool_atm" default_pool_writer="pool_atm" default_pool_reader="pool_atm"> 
    33 
    44  <calendar type="Gregorian" time_origin="1850-01-01 00:00:00" /> 
    55 
    … …  
    314314 
    315315 <file_definition  type="one_file" > 
    316316 
    317     <file id="atm_output" output_freq="1ts" type="one_file" enabled="true"> 
     317    <file id="atm_output" output_freq="1ts" type="one_file" enabled="true" mode="write" using_server2="true"  gatherer="gatherer1" writer="writer1" > 
    318318      <field field_ref="field3D"    enabled="true"/> 
    319319      <field field_ref="field2D"    enabled="true"/> 
    320320      <field field_ref="field_X"    enabled="true"/> 

  • context_oce.xml

     
    11<!-- --> 
    2 <context id="oce"> 
     2<context id="oce" default_pool_gatherer="pool_ocean" default_pool_writer="pool_ocean" default_pool_reader="pool_ocean"> 
    33 
    44  <calendar type="Gregorian" time_origin="1850-01-01 00:00:00" /> 
    55 
    … …  
    314314 
    315315 <file_definition  type="one_file" > 
    316316 
    317     <file id="oce_output" output_freq="1ts" type="one_file" enabled="true"> 
     317    <file id="oce_output" output_freq="1ts" type="one_file" enabled="true" mode="write" using_server2="true"  gatherer="gatherer2" writer="writer2" > 
    318318      <field field_ref="pressure"  /> 
    319319      <field field_ref="field3D_resend" /> 
    320320 

  • iodef.xml

     
    102102        <variable id="check_event_sync" type="bool">true</variable> 
    103103      </variable_group> 
    104104    </variable_definition> 
     105<pool_definition> 
     106<pool name="pool_atm" global_fraction="0.5"> 
     107  <service name="gatherer1" nprocs="2" type="gatherer"/> 
     108  <service name="writer1" nprocs="1" type="writer"/> 
     109</pool> 
     110<pool name="pool_ocean" global_fraction="0.5" > 
     111  <service name="gatherer2" nprocs="2" type="gatherer"/> 
     112  <service name="writer2" nprocs="1" type="writer"/> 
     113</pool> 
     114</pool_definition> 
    105115  </context> 
    106116 
    107117</simulation> 

  • param.def

     
    11&params_run 
    22duration='4ts' 
    3 nb_proc_atm=1 
    4 nb_proc_oce=0 
     3nb_proc_atm=4 
     4nb_proc_oce=3 
     5nb_proc_surf=0 
    56/ 

XIOS3 has been compiled with intel compilers and intel mpi on an icelake cluster. generic_testcase.exe tests successfully with this setup using traditional, XIOS2 configuration and run with:

mpiexec.hydra -print-rank-map -ppn 1 -np 13 ../bin/generic_testcase.exe

but hangs (seemingly after setting up contexts) when attempted with these xml changes. alisting of the xios_client and xios-server logs is attached. It appears to be trying to work as intended but hangs. Excited by the prospect of taking control over the distribution of resources but failing miserably at this first attempt. Am I missing a key ingredient? If there isn't an obvious error then what is the best way to dig deeper? 


                    		
                  

              

                    #78
                    
                      fixed
                    
                    
                      grid masking attribute incorrect name : mask1, mask2, mask3 ...
                    
                    
                      mhnguyen
                    
                    
                      ymipsl
                    
              

                  

                    Description
                    
                      

In order to be coherent with previous xios convention, rename grid_masking attribute




mask1 -> mask_1d
mask2 -> mask_2d
etc..




Up to mask_7d



                    		
                  

      
  

  

    
      ←
    
      
        16
      
      
        17
      
      
        18
      
      
        19
      
      
        20
      
      
        21
      
      
        22
      
      
        23
      
      
        24
      
      
        25
      
      
        26
      
      
        27
      
      
        28
      
      
        29
      
      
        30
      
      
        31
      
      
        32
      
      
        33
      
      
        34
      
      
        35
      
      
        36
      
    
      →
    




      

      

      
Note: See TracQuery
        for help on using queries.