====================
Tutorial start guide
====================


This tutorial is a starter’s guide to running a dummy experiment with Autosubmit.

Dummy experiments run workflows with non-expensive empty tasks and therefore are ideal for teaching and testing purposes.

Real experiments instead run workflows with complex tasks. To read information about how to develop parameterizable tasks for Autosubmit workflows, refer to :ref:`develproject`.

Pre-requisites
==============

Autosubmit needs to establish **password-less SSH connections** in order to run and monitor workflows on remote platforms.

Ensure that you have a **password-less** connection to all platforms you want to use in your experiment. If you are unsure how to do this, please follow these instructions:

- Open a terminal and prompt ```ssh-keygen -t rsa -b 4096 -C "email@email.com" -m PEM```
- Copy the resulting key to your platform of choice. Via SCP or ssh-copy-key.

Description of most used commands
=================================

.. list-table::
    :header-rows: 1
    :widths: 20 80

    * - Command
      - Short description
    * - **expid**
      - Creates a new experiment and generates a new entry in the database by giving it a serial id composed of 4 letters. In addition, it also creates the folder experiment and the basic folder structure.
    * - **create <expid>**
      - Generates the experiment workflow.
    * - **run <expid>**
      - Euns the experiment workflow.
    * - **monitor <expid>**
      - Shows the experiment workflow structure and status.
    * - **inspect <expid>**
      - Generates Autosubmit scripts and batch scripts for inspection, by processing the tasks’ templates with the experiment parameters.
    * - **refresh <expid>**
      - Updates the project directory.
    * - **recovey <expid>**
      - Recovers the experiment workflow obtaining the last run complete jobs.
    * - **setstatus <expid>**
      - Sets one or multiple jobs status to a given value.


Create a new experiment
=======================

    ``autosubmit expid -dm -H "local" -d "Tutorial"``

- *-dm: Generates a dummy experiment.*
- *-H: Sets the principal experiment platform.*
- *-d: Sets a short description for the experiment.*

The output of the command will show the expid of the experiment and generate the following directory structure:

.. list-table::
    :header-rows: 1
    :widths: 20 80

    * - Experiment folder
      - Contains
    * - conf
      - Experiment configuration files.
    * - pkl
      - Workflow pkl files.
    * - plot
      - Visualization output files
    * - tmp
      - Logs, templates and misc files.
    * - proj
      - User scripts and  project code. (empty)


Then, prompt ``autosubmit create <expid> -np`` and Autosubmit will generate the workflow graph.

Run and monitoring:
===============
 To run an experiment, use ```autosubmit run <expid>```. Autosubmit run experiments performing the following operations:

 - First, it **checks the experiment configuration**. If it is wrong, it won't proceed further.
 - Second, it **runs the experiment while retrieving all logs** from completed or failed tasks as they run.
 - Third, it manages all the **workflow steps by following the dependencies defined by the user** until all jobs are in COMPLETED or FAILED status. There can be jobs left in WAITING status if their dependencies are in FAILED status.

While the experiment is running, it can be visualized via ``autosubmit monitor <expid>``.

.. figure:: workflows/dummy.png
   :name: dummy_workflow
   :width: 100%
   :align: center
   :alt: experiment_view

illustrates the output of the autosubmit monitor. It describes all workflow jobs' possible status and actual status.


At the same time, the ``<expid>/tmp`` gets filled with the cmd scripts generated by Autosubmit to run the local and remote tasks (in this case, they are sent and submitted to the remote platform(s)).

On the other hand, the ``ASLOGS`` and ``LOG_a000`` folders are filling up with AS command logs and jobs logs.

Configuration summary:
==================

 In the folder ``<expid>/conf`` there are different files that define the actual experiment configuration.

.. list-table::
    :header-rows: 1
    :widths: 20 80

    * - File
      - Content
    * - ``expdef.conf``
      -
        * It contains the default platform, the one set with -H.
        * Allows changing the start dates, members and chunks.
        * Allows changing the experiment project source ( git, local, svn or dummy)
    * - ``platforms.conf``
      -
        * It contains the list of platforms to use in the experiment.
        * This file contains the definitions for managing clusters, fat-nodes and support computers.
        * This file must be filled-up with the platform(s) configuration(s).
        * Several platforms can be defined and used in the same experiment.
    * - ``jobs.conf``
      -
        - It contains the tasks' definitions in sections. Depending on the parameters, one section can generate multiple similar tasks.
        - This file must be filled-up with the tasks' definitions.
        - Several sections can be defined and used in the same experiment.
    * - ``autosubmit.conf``
      -
        - This file contains the definitions that impact the workflow behavior.
        - It changes workflow behavior with parameters such as job limitations, remote_dependendies and retrials.
        - It extends autosubmit functionalities with parameters such as wrappers and mail notification.
    * - ``proj.conf``
      -
        - This file contains the configuration used by the user scripts.
        - This file is fully customizable for the current experiment. Allows setting user- parameters that will be readable by the autosubmit jobs.



Final step: Modify and run
==========================

 It is time to look into the configuration files of the dummy experiment and modify them with a remote platform to run a workflow with a few  more chunks.

 Open expdef.conf

.. code-block:: INI

    [DEFAULT]
    EXPID = a000 #<- don't change
    HPCARCH = local # Change for your new main platform name, ej. marenostrum4

    # Locate and  change these parameters, per ej. numchunks = 3
    [experiment]
    DATELIST = 20000101
    MEMBERS = fc0
    NUMCHUNKS = 1
    (...)

Now open platforms.conf. Note: This will be an example for marenostrum4

.. code-block:: INI

    [marenostrum4]
    # Queue type. Options: ps, SGE, LSF, SLURM, PBS, eceaccess
    TYPE = slurm # scheduler type
    HOST = mn1.bsc.es,mn2.bsc.es,mn3.bsc.es
    PROJECT = bsc32 # <- your project
    USER = bsc32070 # <- your user
    SCRATCH_DIR = /gpfs/scratch
    ADD_PROJECT_TO_HOST = False
    # use 72:00 if you are using a PRACE account, 48:00 for the bsc account
    MAX_WALLCLOCK = 02:00
    # use 19200 if you are using a PRACE account, 2400 for the bsc account
    MAX_PROCESSORS = 2400
    PROCESSORS_PER_NODE = 48
    SERIAL_QUEUE = debug
    QUEUE = debug

``autosubmit create <expid>** (without -np)`` will generate the new workflow and ``autosubmit run <expid>`` will run the experiment with the latest changes.