|
Minutes (draft) of the AROME-ALARO-ALADIN meeting, February 13, 2004, PragueParticipants1) OpeningThe 'AAA' (AROME-ALARO-ALADIN) meeting was opened by Dr. Ivan Obrusnik, Director of CHMI & Vice-Chairman of the RC LACE Council. 2) Adoption of the AgendaD. Giard proposed two changes in the Agenda (DRAFT VERSION APPENDED): 3) Introductory talks on the general constraints of the considered projectsIntroductory talks were given by J.-F. Geleyn, G. Hello, F. Bouttier and D. Klaric. 4) Round table discussion of transversal problemsThe discussion started by reopening the questions from the last AA meeting (April 2003, Prague). Soon it turned out that the main point to be answered is, whether we (ALADIN Partners) need ALARO or not. In other words, do we need one transition (ALADIN -> AROME) or two (ALADIN -> ALARO -> AROME) ? The first transition (ALADIN -> ALARO) shall be understood as the change of the source code, and it shall be harmonized within the Partners as much as possible (preferably within one model cycle). The reason is, that the file structure will change, also externalization of some tools is expected (e.g. surface scheme). This event, from the point of coordination shall be similar to the change of the ISBA surface scheme in 1998. The second transition will be in the means of cost (CPU, Memory) when starting to use the AROME model (or some of its advanced components). Scheduling of this second step can be left on individual choices and opportunities of each Partner. It was mentioned that, given the pressure of the forecasters and directors to continuously improve our NWP models, no calm period to concentrate on AROME development only can be expected. Also, many NWP groups expressed their problems either with the manpower to be devoted to R&D tasks or with the money to buy computer strong enough to run AROME model. Thus they prefer an intermediate model for their applications. Meteo-France would probably also need a model with about 10km resolution to couple AROME with it (at the same time Météo-France promises to maintain ALADIN software as long as any of the Partners would really need it). On the other hand it shall be kept in mind that the intermediate step via ALARO model will require additional man-power. Especially some duplication of the work can be envisaged in the field of physics. Three potential problems worthwhile to be worked on within 2-3 years (ALARO shall be working in 2006) were identified: Also the worry was expressed that splitting the work between too many (sub-)projects can slow down the progress of the model evolution. However, ALADIN Partners opt for more transitions in their NWP applications. They are aware that the higher level of work coordination and organization will be needed. Thus, the question of the work coordination was again raised. First, it was stressed that Meteo-France has devoted two persons to ALADIN-2 project and that they can also finance the work of external people on the project ("seeding money" in the vocabulary of P. Courtier). It is desirable that ALADIN Partners dedicate special man-power to ALADIN-2. LACE would finance such coordination work as well. The persons to be contacted in case of interest to work on particular topic were identified: The "tool-box" sub-project name was found to be puzzling and not well understandable, and it was proposed to change it to "interfaces". Concerning the code evolution, it was mentioned that the rules of phasing will be provisionally broken. Phasing will be less often, the first back-phasing of the AROME development into ALADIN code is expected in 2005. Also the notice was given of mesoNH physics not following the IFS coding standards. 5) Recall on the way how the preparatory documents for the 2004 work plan were built up and on the contributions used for itG. Hello recalled how the ALADIN-2 working plan for 2004 was prepared. 6) Detailed study of the draft plan, preparation of a more complete version7) Synthesis on the 2004 working plan, balancing of the available contributions across sub-projects and thematics, consequence on the Toulouse staysThe discussion on both Points 6 and 7 is summarized below: NO DETAILS ARE GIVEN HERE, SINCE EVERYTHING IS ALREADY INCLUDED IN THE UPDATED WP AVAILABLE ON THE WEB. The WP will now be updated according to the decisions taken on this meeting and made available to ALADIN Partners. They shall discuss it internally and then concerned people may contact directly the topic coordinator (and keep informed the project coordinators as well as mentioned above). 8) Programation of the next stepsOther coordination meetings similar to this AAA shall be organized during: (As pointed out by D. Giard, this plan might be too ambitious as a lot of money will be needed for so many implied travels.) 9) Definition of priority topics for the Innsbruck 2004 ALADIN workshopY. Wang recalled the date and the venue of the 14th ALADIN workshop. D. Giard raised the question on the special topics to be discussed during this workshop apart of the already announced one (Deep convection in the grey zone). The following suggestions has been made: 10) Decisions concerning the calendar and scope of the "extended Split Assembly"The 9th Assembly of ALADIN Partners is scheduled for the last week of October 2004 in Split, Croatia. Due to the importance of the topics to be discussed there (see below) it was proposed to have one and half or two days meeting (Friday and Saturday). There shall be separate LACE session meeting organized one day prior the Assembly (Thursday). The Assembly shall focus on the preparation of next MoU which would reflect new situation (new project ALADIN-2) and on its consequences. The main topics for the discussions and their input shall be carefully prepared. The repetition of the "ACTIM'96" event shall be considered. The absence of the Minutes from the previous Assembly in Cracow, as the first input, was regretted. In order not to disturb the attention, some "usual" items from the Agenda can be omitted (e.g. the manpower commitments). Also it was suggested to prolongate the validity of the ALADIN research plan for one year, so it matches with the validity of the MoU. There shall be an official letter to all directors describing the latter proposal (BUT WHO WILL WRITE IT? THIS WAS NOT DISCUSSED). If accepted, the evaluation of the ALADIN research plan will not take place on the 9th Assembly. Noting the tendency of the last Assemblies and the importance of the forthcoming one it was stressed that the participation of all directors is of big importance. The invitation of HIRLAM and ECMWF representatives to the Split Assembly was also recommended. All this effort shall culminate at the 10th Assembly of ALADIN Partners to be held in Bratislava, Slovakia (preliminary November 2005) by signing of a new Memorandum of Understanding. 11) AOBCooperation with HIRLAM: J.-F. Geleyn summarized the history of the HIRLAM & AROME cooperation. The original proposal of their Management Group to deeply collaborate on ALADIN-2/AROME projects was not accepted, nowadays HIRLAM considers to import ALADIN/NH dynamics and to participate on the code, namely on the development of the interface (to be able to plug-in their physics). They will for sure keep their data assimilation and also the name HIRLAM. Also situation can change with the new Project Leader, to be elected in autumn. Due to the above mentioned uncertainties D. Giard suggested to currently suppress the word "HIRLAM" and associated sentences from all strategic documents on ALADIN-2. However, a special training is to be organized in Toulouse on ALADIN and its NH aspects for HIRLAM people during the twelveth week of 2004. A puzzling situation occurred as similar NH training was already required by LACE, because several people consider the change of their main subject to NH dynamics. But, the training in Toulouse is rather for newcomers, with some general lectures on ALADIN etc. Therefore it was proposed to organize separate LACE NH training (in Prague), with added topic focused on "interfaces" and the possibility to re-invite interested HIRLAM people (and other ALADIN countries, of course).
THESE MINUTES ARE COMPLEMENTED BY THE APPENDED ‘DECISIONS SUMMARY’ |