Météo-France ALARO & AROME activities
Météo-France ALARO & AROME activities Météo-France ALARO & AROME activities
Internal CNRM ALARO/AROME workplan - Feb 2005 • Check whether there are issues of stabilities at varying resolutions who: feasibility study by Y. Bouteloup, coding work with E. Bazile, total 1 month. G. « Surface » process aim: to speed up the ARPEGE/ALADIN plugging in of the externalised surface so that ALARO can use it. This is tricky because specific technical development is needed, and some inter-team coordination needs to be organised in CNRM, this process must be split into smaller subtasks. work packages: • develop the surface/diffusion implicit coupling in the ARPEGE/ALADIN Fortran code (P. Marquet et al, 5 months for the ARPEGE-Climate model, this is the most urgent) • implement new features into the external surface code and files, mainly the ALADIN and ARPEGE geometries (P. Le Moigne et al, 3 months, coordination with GMAP, GMME, DSI) • enforce compatibility with the non-model operational ARPEGE/ALADIN configurations, including FullPos, surface and upperair assimilation. Need to start with an inventory of requirements (R. El Khatib, F. Taillefer, F. Bouyssel, J.-M. Audoin, etc., coordination with GMAP, GMME, DSI, total 6 months) There are two additional processes, « Symmetric compatibility » and « Grey zone physics », which are not done in Toulouse except perhaps for some help in running 1D intercomparisons between Alaro and MésoNH (help from S. Malardel and G. Hello) _______ On top of these ALARO actions, limited supporting work by GMAP/PROC and G. Hello will be given (typically, to run tests: e.g. on radiation). G. Hello shall also publish the corrected results from the AROME-10km test cases. 8
Internal CNRM ALARO/AROME workplan - Feb 2005 III. Implied workload on CNRM staff The unit is the person.month; multiple-person actions are either shared or allocated to the first cited person, depending on what is most likely to happen. The action numbers are given between square brackets. The names are sorted in alphabetic order. For G. Hello, S. Malardel and Y. Seity we also mention the particularly large number of 'minor' tasks (management and training) which will add up to a few extra person.months . For most people there will be some added workload for the ALADIN meeting in Slovakia (June 05), too. L. Auger 0.5 [G] J.-M. Audoin 2 [1a] + 2 [G] E. Bazile 2 [B] + 0.5 [F] Y. Bouteloup 0.5 [F] F. Bouttier 0.5 [1b] F. Bouyssel 0.5 [G] G. Casagrande 3 [4d] R. El Khatib 0.5 [1b] + 2 [G] J.-D. Gril 1 [G] G. Hello 0.5 [1b] + 0.5 [2c] + 1 [3c] + 1 [B] + 12 'minor' tasks C. Lac 0.5 [2b] + 2 [Ei] + 0.5 [Eiii] P. Marquet 5 [G] V. Masson 0.5 [1a] + 0.5 [G] P. Le Moigne 0.5 [1a] + 3 [G] S. Malardel 0.5 [1a] + 0.5 [2b] + 0.5 [2c] + 3 [5] + 1 [A] + 5 'minor' tasks J.-M. Piriou 2 [6] + 1 [C] Y. Seity 1 [2a] + 0.5 [2b] + 3 [3a] + 1 [D] + 7 'minor' tasks F. Taillefer 1 [G] K. Yessad 1 [2a] + 0.5 [3c] (visitor on surface interface 6 [2] if recruited) (GMME work [E] on Méso-NH physics and operations-oriented extra work on the externalised surface [G] not yet quantified) Conclusion: this adds up to about 39 person.months, when one includes holidays and the overhead of 'small' tasks, this amounts to about 7 full-time staff, including more than 2 on ALARO-specific work. 9
- Page 1 and 2: Internal CNRM ALARO/AROME workplan
- Page 3 and 4: Internal CNRM ALARO/AROME workplan
- Page 5 and 6: Internal CNRM ALARO/AROME workplan
- Page 7: Internal CNRM ALARO/AROME workplan
Internal CNRM <strong>ALARO</strong>/<strong>AROME</strong> workplan - Feb 2005<br />
• Check whether there are issues of stabilities at varying resolutions<br />
who: feasibility study by Y. Bouteloup, coding work with E. Bazile, total 1 month.<br />
G. « Surface » process<br />
aim: to speed up the ARPEGE/ALADIN plugging in of the externalised surface so that<br />
<strong>ALARO</strong> can use it. This is tricky because specific technical development is needed, and<br />
some inter-team coordination needs to be organised in CNRM, this process must be split<br />
into smaller subtasks.<br />
work packages:<br />
• develop the surface/diffusion implicit coupling in the ARPEGE/ALADIN<br />
Fortran code (P. Marquet et al, 5 months for the ARPEGE-Climate model, this is<br />
the most urgent)<br />
• implement new features into the external surface code and files, mainly the<br />
ALADIN and ARPEGE geometries (P. Le Moigne et al, 3 months, coordination<br />
with GMAP, GMME, DSI)<br />
• enforce compatibility with the non-model operational ARPEGE/ALADIN<br />
configurations, including FullPos, surface and upperair assimilation. Need to<br />
start with an inventory of requirements (R. El Khatib, F. Taillefer, F. Bouyssel,<br />
J.-M. Audoin, etc., coordination with GMAP, GMME, DSI, total 6 months)<br />
There are two additional processes, « Symmetric compatibility » and « Grey zone<br />
physics », which are not done in Toulouse except perhaps for some help in running 1D<br />
intercomparisons between Alaro and MésoNH (help from S. Malardel and G. Hello)<br />
_______<br />
On top of these <strong>ALARO</strong> actions, limited supporting work by GMAP/PROC and G. Hello<br />
will be given (typically, to run tests: e.g. on radiation). G. Hello shall also publish the corrected results<br />
from the <strong>AROME</strong>-10km test cases.<br />
8
Change language