| 109 | | This page describe the different ORCHIDEE versions. Only physical or important informatic |
| 110 | | differences will be describe. Then no line cut nore modifications in comments in this description.[[BR]] |
| 111 | | |
| 112 | | To get a specific version of ORCHIDEE, you can use this alias in your .cshrc : |
| 113 | | {{{ |
| 114 | | alias cvs_orc 'cvs -d :pserver:sechiba@cvs.ipsl.jussieu.fr:/home/ssipsl/CVSREP' |
| 115 | | }}} |
| 116 | | You must have ORCHIDEE source login/password registred in your ~/.cvspass file. [[BR]] |
| 117 | | You must ask Martial Mancip (or other authorized ORCHIDEE group members) |
| 118 | | for login/password to access to the protected source (not by mail) - see |
| 119 | | [http://www.ipsl.jussieu.fr/~mmaipsl Martial Mancip] for contact. |
| 120 | | |
| 121 | | When this configuration is set correctly (and adapted if your login shell is bash or other), |
| 122 | | you can get a specific orchidee_version_to_get with the simple command : |
| 123 | | {{{ |
| 124 | | prompt> cvs_orc co -r orchidee_version_to_get ORCHIDEE |
| 125 | | }}} |
| 126 | | For branch TAGs only, you must specify the date of the beginning of the branch, otherwise you will |
| 127 | | get le last point of the branch by default : |
| 128 | | {{{ |
| 129 | | prompt> cvs_orc co -r orchidee_branch_to_get -d the_date ORCHIDEE |
| 130 | | }}} |
| 131 | | |
| 132 | | |
| 133 | | A presentation of differencies between versions 1.3 - 1.6 and series 1.9 is here : |
| 134 | | * http://dods.ipsl.jussieu.fr/orchidee/point_version_1.3-1.6-1.9.pdf |
| 135 | | * http://dods.ipsl.jussieu.fr/orchidee/Bilan_Passage1.4_A_1.5.doc |
| 136 | | |
| 137 | | == Models and Configurations == |
| 138 | | Model ORCHIDEE can be reach at link |
| 139 | | [http://forge.ipsl.jussieu.fr/orchidee/viewvc/?root=orchidee ORCHIDEE source]. |
| 140 | | |
| 141 | | Each ORCHIDEE versions are validated with three sort of runs : |
| 142 | | * OFF-LINE mode : |
| 143 | | * that is for ORCHIDEE group the mode with ORCHIDEE_OL driver. |
| 144 | | Please have a look on [http://orchidee.ipsl.jussieu.fr/ ORCHIDEE Scientific Web] |
| 145 | | * In this configuration, we use atmospheric climatology to force the surface model. |
| 146 | | There are two sorts of atmospheric datas : |
| 147 | | * NCC datas high frequency (6 hours average) in one degree resolution. |
| 148 | | The model will interpolate them to obtain half hour |
| 149 | | time step values. |
| 150 | | * WG_cru file with monthly average datas. |
| 151 | | The driver has a special mode to generate half hour time step values. |
| 152 | | The resolution can change from half degree to four degrees. |
| 153 | | * Most versions were tested with NCC files with 20 years runs from 1980 to 1999. |
| 154 | | Then we compare last 10 years averages. |
| 155 | | * ON-LINE mode : |
| 156 | | * that is for ORCHIDEE group the mode where ORCHIDEE is built as a module of the |
| 157 | | atmospheric model LMDz4 (see [http://web.lmd.jussieu.fr/cgi-bin/viewvc.cgi/LMDZ4/ LMDZ4]). |
| 158 | | * In this configuration, we use a 96x71 grid to validate TO DO. |
| 159 | | * Couple mode : |
| 160 | | * that is the Global Climate Model of IPSL. |
| 161 | | See [http://igcmg.ipsl.jussieu.fr/ IGCMG Web] and [http://forge.ipsl.jussieu.fr/igcmg IGCMG Models] for more |
| 162 | | informations. |
| 163 | | * In this configuration, we have all IPSL climate models coupled together. |
| 164 | | It is the IPCC configuration. |
| 165 | | |
| 166 | | == Versions == |
| 167 | | |
| 168 | | List of ORCHIDEE TAGs and Branchs and TAG action date : |
| 169 | | |
| 170 | | == Difference between versions == |
| 171 | | |
| 172 | | To see difference between version, you have to get both version in local (namely orchidee_path_1, |
| 173 | | orchidee_path_2). Then you can apply two commands to see informations between versions : |
| 174 | | {{{ |
| 175 | | diff -w --ignore-all-space --ignore-case --recursive --exclude="Entries" --exclude="Tag" \ |
| 176 | | orchidee_path_1/ORCHIDEE/ orchidee_path_2/ORCHIDEE/ > diff_1-2.f90 |
| 177 | | }}} |
| 178 | | And to get log informations with date1 and date2 refered respectively to TAG actions dates |
| 179 | | for version1 and version2 (see TAG informations above) : |
| 180 | | {{{ |
| 181 | | cvs log -d 'date1+1<date2' > cvs_log_diff_1_2-1_3 |
| 182 | | }}} |
| 183 | | note : |
| 184 | | 1. I put "date1+1" that means "date1 + 1 day" because you only want to see commit messages |
| 185 | | after version1 TAG. [[BR]] For example, orchidee_1_1 has been tagged the 12/04/2002. Then you must use |
| 186 | | date1+1 = 12/05/2002 (dates for CVS are in american format). |
| 187 | | 2. You will get all informations on commits between the two dates. Then you will get some commit messages |
| 188 | | on other branch too if there are some. |
| 189 | | |
| 190 | | |
| 191 | | |
| 192 | | |
| 193 | | |
| 194 | | |
| 195 | | |
| 196 | | |
| 197 | | |
| 198 | | |
| 199 | | |
| 200 | | |
| 201 | | |
| 202 | | |
| 203 | | == Validations == |
| 204 | | |
| 205 | | See page ValidateOrchidee. |
| 206 | | |
