HELIOGate, a Portal for the Heliophysics Community - Science Gateways for Distributed Computing Infrastructures - page 195

performed in the input operation: check that all the expected files are present

and check that their content is consistent.
3. Environment setup: Once data has been passed to the node, and its consis-
tency has been checked, the processing environment can be set up.
4. Processing: Once data has been passed to the node, its consistency has been
checked, and the processing environment has been successfully set-up, the
processing itself is performed.
5. Environment tear down: After processing is completed, the environment can
be cleared.
6. Data output: Data produced by the processing is written to

files.

14.6 Architecture

The software structure of HELIOGate (Fig. 14.4 ) is multilayered and has at the top
a set of user interfaces. WS-PGRADE offers interfaces used by advanced users to
design and execute the workflows and simple interfaces used by domain researchers
to execute template workflows for propagation modelling and data processing. The
interface layer also comprises the advanced propagation model portlet for domain
researchers who find acceptable the constraints enforced by this specific

implementation.
The advanced propagation model portlet is connected to the gUSE service layer
through the ASM API interface for the management and execution of workflows.

Fig. 14.4 Architecture of HELIOGate