Changes between Version 2 and Version 3 of GroupActivities/Meetings/Retreat20151119/GuidelinesXIOS


Ignore:
Timestamp:
2015-10-12T09:25:30+02:00 (9 years ago)
Author:
jgipsl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GroupActivities/Meetings/Retreat20151119/GuidelinesXIOS

    v2 v3  
    11= XIOS Guidelines 
    22 
    3 * '''Guideline 1''' (to be discussed)[[BR]] 
     3== '''Guideline 1''' (to be discussed) == 
    44''Example1:'' 
    55{{{ 
    … …  
    5656=> In this case, soilflx becomes GroundHeatF directly. 
    5757 
    58 * '''Guideline 2''' 
    59 We do the "CALL XIOS send_file orchid" in the module where the variable is calculated. If the variable is changed in several places, we do the call in the last XIOS module where it is changed or in sechiba_main, this has to be decided case by case. 
     58== '''Guideline 2''' == 
     59We do the "CALL xios_orchidee_send_field" in the module where the variable is calculated. If the variable is changed in several places, we do the call in the last XIOS module where it is changed or in sechiba_main, this has to be decided case by case. 
    6060 
    61 * '''Guideline 3'''  
     61== '''Guideline 3''' == 
    6262If the variable is only calculated for a specific run case, then we deactivate the output from xios_orchidee.f90 with xios_set_field_attr as for the case not calculated. This leaves us the possibility of having the same file_def_orchidee.xml for different setups. If we forgot, it will work but we will have declared variables in the .nc files without values, which is is troubling. As an exception, the stomate variables are not deactivated in this way, that would be too many exception cases. But since we traditionally separated variables between sechiba_history.nc and stomate_history.nc, we have no problem because we deactivate the whole stomate_history.nc file if stomate is not active. 
    6363