Changes between Version 10 and Version 11 of ticket/930


Ignore:
Timestamp:
28/01/11 22:36:10 (2 years ago)
Author:
charlotte
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ticket/930

    v10 v11  
    109109||'''Questionnaire Experiment Name'''||'''Experiment name in xml output (after conflation)'''|| 
    110110||decadal||decadal1960|| 
    111 ||tri-decadal||decadal1960|| 
     111||decadal-30yr||decadal1960|| 
    112112||decadal-E||decadal1960|| 
    113113||decadal-I||decadal1960|| 
    114114 
    115 So the distinct decadal experiment are there to guide the user - the user sees familiar experiment names that match with the concepts in the Taylor et al CMIP5 experiment design document.  The distinct decadal experiment names also help the tools to answer Bryan's questions above. 
     115So the distinct decadal experiments are there to guide the user - the user sees familiar experiment names that match with the concepts in the Taylor et al CMIP5 experiment design document and distinct decadal experiment names allow the tools to answer Bryan's queries above. 
     116 
     117Applying the method to the HistoricalMisc experiments would allow us to show users a list of individual forcing experiments but generate a list of HistoricalMisc experiments for the xml output.  I like this idea because it prevents users having to "untick" a long list of requirements that don't apply when they tell us how their simulations conformed to the experiment.  But I know that Bryan has a presumption against this.  Nevertheless if we can apply this method then this is what we'd have. 
     118 
     119||'''Questionnaire Experiment Name'''||'''Experiment name in xml output'''|| 
     120||HistoricalSO|| HistoricalMisc|| 
     121||HistoricalSI|| HistoricalMisc|| 
     122||HistoricalSS|| HistoricalMisc|| 
     123||...||...||