Changes between Version 2 and Version 3 of WorkingGroups/ConfigurationManager

Timestamp:

2013-02-25T09:21:48+01:00 (11 years ago)

Author:

jpaul

Comment:

--

WorkingGroups/ConfigurationManager

@@ -6 +6 @@
 This working group (and wiki pages) are under the responsibility of Julien Paul
 
-The next step is to define what the configuration manager should be able to do or not in the next release of NEMO. We have to choose some hypothesis, limits, and moreover to choose which tools to be used.
+The goals of this discussion is to define what will do or not the config manager in the next release of NEMO. 
 
-You could find the updated document below.
+The first step is to define:
 
-In part 3, you could find the list of tools that could be used in the configuration manager, depending of which input files we get. Of course we could still add other tools to this list. However we have to start to choose which tools to be used as references and so should be maintain by NEMO team.
+ * what do we need to create regional configuration
+ * how each team do it now
+   * methods
+   * language
+   * limits of these methods
 
-I think we should use free licence language, so it will be easiest for all user. I propose to use Fortran and python. Moreover, as AM Treguier said, it will be more efficient to use the same tools than in AGRIF, to minimize number of codes to maintain.
+'''Schedule:'''
 
-Finally, in the same time we continue to discuss on it, I propose to build a demonstrator (see part 4). 
+ 1. list method used now (>23 Jan)
+ 1. list idea to solve some limitations (> 03 Feb)
+ 1. Define what will do or not the config manager in the next release of NEMO (> 20 Feb)
+
+The schedule is voluntarily short. First, cause this part should have be done last year. Moreover, if we want to have something reliable to put in the next release of NEMO, we must start to merge tools and write skeleton of the config manager at least in Marsh.