Changes between Version 2 and Version 3 of Tags/196/ExternalisationParameters/UsersGuide

Timestamp:

2011-03-18T15:45:54+01:00 (13 years ago)

Author:

dsolyga

Comment:

--

Tags/196/ExternalisationParameters/UsersGuide

@@ -3 +3 @@
 This page is a copy of the file you could find in the folder Doc_externalised_version/ when
 you download ORCHIDEE_EXT. [[BR]]
+
 
 == Global specifications ==
@@ -282 +283 @@
 == Other aspects ==
 
-
-
-
-
-
-
-
+-In order not to have a « big » file filled with 300 parameters and all their default values, the new « orchidee.def » file contains no default values. It lists only the description of the  parameters anf their key words. You find an example here :
+{{{
+# Vegetation distribution within the mesh (0-dim mode)
+# If IMPOSE_VEG
+# The fraction of vegetation is read from the restart file. 
+#  If it is not found there we will use the values provided here.
+# SECHIBA_VEG
+}}}
+The goal is that « orchidee.def » will be filled only by the values the user imposed. You could easily see the new values of the parameters. (see « How can you control your values after your job »).You will find all the default values and their types by two different ways :  there are files called « orchidee_run_parameters.txt »,  « sechiba_parameters_default_values.txt » and « stomate_parameters_default_values.txt »which list all the default values used in the code. This is the « user's » way. The second is the « developper's » way : look at the files called « constantes.f90 » and « constantes_mtc.f90 » in the src_parameter folder.
+
+'''PS :'''The next objective will be to divide « orchidee.def » in three parts : « orchidee_run.def » which will contain all the global options for a job, « sechiba_parameters.def » and « stomate_parameters.def » «containing respectively the specific  parameters for sechiba and for stomate.
+
+-Only for the PFT parameters,  you can use an option called IMPOS_PARAM. If you set it to FALSE, all the new values you put to the PFT parameters won't be read.  If you make many changes for one job and you want to compare with the default values, you don't need to comment the values you impose. We think about the same mechanism for the other parameters (you could find all them in constantes.f90).
+
+-Except for PFT_TO_MTC and a few exceptions, the values of the parameters you will set are not controled. (We can't put 300 barriers) Read the different « .txt » files before making some changes. 
+
+ErrorsMessages
+
+== MARCH 2011 ==
+
+'''PS : '''In the most recent version of ORCHIDEE, you will find three files instead of "orchidee.def". These
+files are called "driver.def","sechiba.def" and "stomate.def". You can choose to define your parameters
+in any of these files because ORCHIDEE can make the merge. 
+
+
+
+=== ''Advice for developpers only'' ==
+
+Our strategy was to centralize all the parameters in src_parameters. We think that this is better for the maintenance. 
+
+If some people for their developpements want to add a new permanent metaclass or a new pft parameter (like Q10), they only have to modify the file constantes_mtc.f90 and add all the new values (don't forget to change the parameter 'nvmc' representing the number of MTCs).
+
+
+
+
+
+