process. In fact, the smartphone application drive for 
quality visualization, interaction, speed, and 
availability has been established by feedback from 
the two-thirds of the American population (Smith, 
2015) who own smartphones and a median value of 
54% of smartphone users (billions) in emerging or 
developing countries (Poushter, 2015).  
It is clear that new application interaction and 
design practices which are commonly accepted in 
social and recreational smartphone application 
activities are a paradigm beyond traditional 
approaches (Ito, 2009) for HPC modeling. These 
new interaction design practices impact what forms 
of learning younger generations value and potential-
ly point the way for new workflow practices to be 
adopted. Adoption of these new practices can impro-
ve the quality of the workflow for more mature 
generations and creates workflow which is already 
natural to the younger developing generations. 
The intent of the MEDEA experiment was to 
establish a seamless workflow between the user and 
the HPC code. To the extent possible the input deck 
paradigm should be transparent to the user, requiring 
only key values of parametric input and a “run 
button”. Post-processing of results should be 
provided as part of the workflow with elements that 
are aesthetically pleasing. Part of the MEDEA 
experiment also involved the creation of the team 
with the right expertise to make interaction design 
and visualization choices to improve the HPC code 
user workflow. 
 
Figure 1: MEDEA introductory view. Placing the power in 
the hands of the user is the metaphor being invoked. The 
user selects from the three options listed. 
2  MEDEA DESIGN OBJECTIVES 
Prior to the coding of MEDEA, design objectives 
were identified which shaped the development of the 
application. There was a strong desire to place the 
final tool in the hands of the user in such a way that 
the disenfranchised (Ito, 2015) who saw nothing but 
barriers to HPC code simulation would become 
excited and want to explore physical phenomena 
using simulation. The user experience had to bypass 
both issues with operating system availability (run 
on Microsoft Windows) and the hundreds of lines in 
the input deck. Simulation execution should entail 
simple and clean parameter input and one-touch 
simulation execution. 
Advancing the ease-of-use (learnability) of the 
application was important. Previous efforts to teach 
HPC code users have involved days of training. 
Training using simplified input decks with variables 
defined within the top 25 lines could take 20 minutes 
to teach someone how to run the code. The objective 
of MEDEA was to determine if the time to learn 
how to load a simulation model and enter the 
required input could be reduced to minutes, or even 
tens of seconds. 
Another important element to MEDEA was that 
the interface and results should look “cool”. 
Spectacle and fun are commonly used in children’s 
software to demonstrate style and status, they are 
part of the economy of “cool” (Ito, 2009).  
Children’s software typically employs “fun” in order 
to maintain focus for a sufficient amount of time in 
order to solve problems (exploration). Enthusiasm 
associated with fun involves sharing and 
demonstrating with others. These are inherent 
responses we wished to evoke with scientific 
simulation visualization. The child may say a view 
looks “cool”. To the more mature individual it is 
“cool” not only because of aesthetics but because it 
provides visualizations that can be used to explain 
physical phenomena and why you obtained a certain 
level of system performance. An experience is also 
“cool” when one can easily learn from it which is 
also pleasing. Learning with increased ease is “fun”. 
View establishment and simplicity was also a 
desired objective. For a given simulation type there 
might exist a commonly accepted view of the 
results. This type of analysis should be able to 
generated easily and should be a natural result from 
the simulation. In the case of a new analysis which 
might have been published or presented in another 
forum, that view should be easily appended to the 
views already generated. In either case, the views 
should not be cluttered and the user should be 
allowed to interact with the resulting analysis in 
order to query points, make comparisons, or 
simultaneously view multiple variables and how 
they relate to one another.