In this context we can define an Earth Science modeling workflow as the set of individual tasks that are needed to perform a simulation with a weather or a climate model. Tasks may have dependencies between them, i.e. a task can start only when other (parent) tasks have finished successfully. Each task may run in a different platform, usually an HPC system. All these facts increase the complexity of this kind of workflow.

A weather or climate simulation can be divided in different phases, which largely determine the dependencies between the jobs in a workflow:

\begin{center}
\includegraphics[width=0.9\textwidth]{workflow_phases.png}
\end{center}

In Autosubmit, a complex workflow may look like this:

\begin{center}
\includegraphics[width=0.8\textwidth]{workflow.png}
\captionof*{figure}{\color{NavyBlue} Example of a complex workflow created with Autosubmit. Each box is a job, i.e. an individual step in the workflow. The arrows represent the dependencies between jobs and the colors represent the current status of each job.}
\end{center}

%The main features of Autosubmit are:
%
%\begin{itemize}
%\item \textbf{Automatization}: orchestrating different kind of tasks and environments without intervention.
%\item \textbf{Provenance and reproducibility}: unique experiment IDs, storing all the parameters needed to reproduce them (Autosubmit version, model version, configuration, etc.). 
%\item \textbf{Failure tolerance}: automatic retrials and ability to rerun chunks in case of corrupted or missing data, repeating postprocessing and transfers if needed. Recovery capabilities.
%\item \textbf{Versatility}: variety of workflows supported, from Auto-Models to data-centric or performance analysis, with different potentialities for each case.
%\end{itemize}
