Changes between Version 4 and Version 5 of Documentation/UserGuide/NewFlag

Timestamp:

2020-03-19T17:03:42+01:00 (4 years ago)

Author:

bguenet

Comment:

--

Documentation/UserGuide/NewFlag

@@ -1 +1 @@
 = How to add a new flag =
 
+Author: D. Solyga [[BR]]
+Last revision: B. Guenet (2020/03/19)
 
 == Declare the new flag ==
@@ -7 +9 @@
 
 {{{
-TYPE control_type
-   LOGICAL :: ok_NameOfNewFlag      !! Explanation of new flag
-END TYPE control_type
+
+   LOGICAL, SAVE :: ok_NameOfNewFlag      !! Explanation of new flag
+!$OMP THREADPRIVATE(ok_NameOfNewFlag)
+
 }}}
 
-Next, you store the flags in a common variable named 'control'. This is done in ../modeles/ORCHIDEE/src_sechiba/sechiba.f90 in the subroutine sechiba_init
+
+== Read the flag from the parameter file ==
+
+Next, you need to read the flag value. Don't forget to wrote a default value. This is done in ../modeles/ORCHIDEE/src_sechiba/sechiba.f90 in the subroutine sechiba_init
 
 {{{
-control%ok_NameOfNewFlag = control_in%ok_NameOfNewFlag
+    ok_NameOfNewFlag=.FALSE.
+    CALL getin_p('OK_NAMEOFNEWFLAG', ok_NameOfNewFlag)
 }}}
 
 [[BR]]
 
-== Read the flag from the parameter file ==
-
-The flag can be read in the routine where you need it, if the flag is shared among routines you can read it in the first common routine. Quite a few flags that control the flow of th emodel are read in intersurf.f90 in the subroutine intsurf_config. Document the flag using the default keywords (see below). An example is shown for the flag called control%ok_functional_allocation 
-
-{{{
-!Config Key  = STOMATE_FUNCTIONAL_ALLOCATION
-!Config Desc = use Friedlingstein etal. 1999 or Zaehle et al 2010 for allocation
-!Config Def  = n
-!Config Help = set to TRUE if functional allocation is to be activated
-!
-control%ok_functional_allocation = .FALSE.
-CALL getin_p('STOMATE_FUNCTIONAL_ALLOCATION',control%ok_functional_allocation)
-WRITE(*,*) 'Allocation is based on plant structure: ',control%ok_functional_allocation
-}}}