TOC(heading=nemo_ConfigurationManager,nemo_ConfigurationManager/*, depth=1)?

nemo_ConfigurationManager

Last edited Timestamp?

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.

You could find the updated document below.

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.

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.

Finally, in the same time we continue to discuss on it, I propose to build a demonstrator (see part 4).