(Jupiter HST Image NASA, ESA, and A. Simon (GSFC))	(Saturn Cassini Image NASA-JPL)

Workshop I Presentations :

Boutsi, Z.: Wavelet Spectral Analysis

Chané, E.: MHD Modelling / Tools

Constable, D.: MHD Modelling of M-I Coupling at Earth

Hardy, F.: Magnetopause Modelling

Pisa, D.: iPECMAN Interface

Ray, L. C.: Magnetosphere-Ionosphere Coupling

Stephens, G. et al: Saturn Magnetospheric Field Model

Sorba, A. M.: Magnetodisc Modelling

Vogt, M.: Auroral Mapping

Yates, J.: Magnetosphere-Ionosphere-Thermosphere Coupling at Jupiter

Workshop Draft Report :

This workshop brought together some expertise in numerical modelling and data analysis related to planetary science. Details of the models / tools discussed can be found in the presentations above. Below is a list of some of the pertinent points which were discussed during the final workshop session.

• Further training workshops of this nature for the community would be advantageous in fostering further collaborations between observers and modellers.
• The caveats under which model ouputs are made available by various means (see below) should be made clear (e.g. citation / authorship arrangements). In practice, this may involve some kind of 'registration / agreeement' on the part of the user.
• These 'various means' emerged during the workshop discussions. Essentially, there are different styles of access to modelling / analysis tools. One way to describe these is according to target groups. For example, tools / repositories may be (initially) restricted to small research groups / instrument teams at one end of the 'spectrum'; all the way through to public access repositories, such as those established via the Europlanet research infrastructure project.
• In addition, many journals currently impose requirements on 'data availability'. For modellers, it is often the case that they have to clarify with the journal the conditions of access to model outputs, and / or modelling code. Journals impose such requirements partly to ensure that published results are 'repeatable' by other parties. In terms of a numerical model, is it sufficient to have an initial publication/s which thoroughly describes the equations / algorithms used to develop the model? In principle, such a publication, with adequate detail, could be designed to be 'reproducible' by others?
• It is a good idea for modelling software developers to familiarize themselves with the intellectual property policy of their host institution, as regards the IP status of software developed by members of staff.
• Naturally emerging scientific collaborations lend themselves well to the distribution of model outputs / data analysis tools and results. Public databases may be useful for a 'first look', but a 'human point of contact' always encourages potential users who will likely have many questions about e.g. the limitations of models / algorithms. Common access protocols and frameworks help to make online data / tools more appealing and 'user friendly'.
• There were also discussions about licencing code developed under the auspices of research infrastructure projects such as Europlanet.

Last Updated: Apr 2019 by N. Achilleos