Changes between Version 10 and Version 11 of NumSim


Ignore:
Timestamp:
15/05/06 13:08:24 (14 years ago)
Author:
lawrence
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • NumSim

    v10 v11  
    66[source:TI01-discovery/trunk/schema/numsim  here]. The proposed schema should be accessible to both [wiki:DIF] and [wiki:ISO19115] parent discovery schema (as it evolves), although at the moment it's rather standalone. 
    77 
    8 The schema is documented in a pdf file which you can download from [source:TI01-discovery/trunk/schema/numsim/NumSim_Documentation.pdf here]. See also example files: 
    9 [source:TI01-discovery/trunk/schema/numsim/HADCM3%20PUM%204.5%20Beowulf.xml HadCM3 Beowulf 500 year run] 
     8The schema is documented primarily through the schema itself, but there is fairly comprehensive documentation in the [source:TI01-discovery/trunk/schema/numsim/Documentation documentation] directory - although note that it tends to lag the schema by a bit - especially the [source:TI01-discovery/trunk/schema/numsim/Documentation/NumSim_Documentation.pdf pdf version]. 
     9 
     10See also example files: 
     11[source:TI01-discovery/trunk/schema/numsim/HADCM3%20PUM%204.5%20Beowulf.xml HadCM3 Beowulf 500 year run], which we do try and keep current. 
    1012 
    1113Comments are welcome! Please note that this version has only just started to be trialled with data, so some changes are inevitable as described below. 
    … …  
    2931=== Planned Changes === 
    3032 
    31 Tasks for milestone releases are listed below by milestone. However, note that not all the tickets listed below will definitely be done, you should look at the ticket status to be sure of what we currently are confirmed to do for each milestone. 
     33The outstanding tasks for milestone releases are listed below by milestone. However, note that not all the tickets listed below will definitely be done, you should look at the ticket status to be sure of what we currently are confirmed to do for each milestone. 
    3234 
    3335==== [milestone:NumSimV007] ==== 
    3436 
    35 [[TicketQuery(Keywords~=NumSim&Milestone=NumSimV007)]]  
     37[[TicketQuery(Keywords=~NumSim&Milestone=NumSimV007&status!=closed)]]  
    3638 
    3739==== [milestone:NumSimV008] ==== 
    … …  
    3941Convergence with [http://www.cgam.nerc.ac.uk/pmwiki/NMM/index.php/ Numerical Model Metadata]. What we want to be able to do is generate NumSim entries from NMM descriptions.  
    4042 
     43Complete ISO19139 compliance as an extension to the WMO core profile. 
    4144 
    4245[[TicketQuery(Keywords~=NumSim&Milestone=NumSimV008)]]  
    … …  
    5356 
    5457 1. We could support individual members of the climate prediction ensembles by adding to the model element an optional <perturbed> element which could be a list made up of arg param pairs. These would appear in ensemble member descriptions but not in grand ensemble descriptions. The usual issue of what level in the D heirarchy should be exposed to the wider world will arise.  
    55  1. Should we have the initial conditions as attributes (subelements) of the Model rather than as attributes of the simulation. This would help in some regards, but might break the future ability to inherit model descriptions ... Note that Response 2.4 is unkeen on this. ''Seems unlikely at the moment'' 
     58 1. Should we have the initial conditions as attributes (subelements) of the Model rather than as attributes of the simulation. This would help in some regards, but might break the future ability to inherit model descriptions ... Note that Response 2.4 is unkeen on this. ''This wont happen as originally concieved since we have split the description up into codebase and experiment ...''' 
    5659 
    5760Trivial