Testing Autosubmit user configuration
Hi @nperez, @cdelgado, @vtorralba and @nmilders
Many thanks for volunteering to test the Autosubmit+Verification Suite development
Here are the instructions on how to test the Autosubmit+Verification Suite development. First, let's all test with the same recipe and script to try to detect problems with different users/user configurations.
You will need to clone the repository and checkout into the dev-autosubmit
branch. Then, follow these steps:
Step 1: Create a new autosubmit experiment. From the terminal, ssh into the autosubmit machine (bscesautosubmit01) and enter the following commands:
module load autosubmit/3.14.0-foss-2015a-Python-2.7.9
autosubmit expid -H nord3v2 -d <Description> # Write anything you like in the description, like "Auto-S2S test" for example.
This will create a new autosubmit experiment which you can use for your verification workflows, with a new ID (EXPID). Save your EXPID somewhere so you remember it. You will not have to do this every time, as you can use this EXPID for other verification runs. It's up to the user how many they want to create.
Step 2: Modify the recipe. We will be using this recipe: recipes/tests/recipe_seasonal_example.yml
. Make a copy and change the fields in the 'Run' section with your personal information:
Run:
Loglevel: INFO
Terminal: yes
filesystem: esarchive
output_dir: /esarchive/scratch/vagudets/repos/auto-s2s/out-logs/ # replace with the directory where you want to save the outputs
code_dir: /esarchive/scratch/vagudets/repos/auto-s2s/ # replace with the directory where your code is
autosubmit: yes
# fill only if using autosubmit
auto_conf:
expid: a5no ## replace with your EXPID
hpc_user: bsc32762 # replace with your hpc username
wallclock: 01:00 # hh:mm
processors_per_job: 8
platform: nord3v2
email_notifications: yes # enable/disable email notifications. Change it if you want to.
email_address: victoria.agudetse@bsc.es # replace with your email address
notify_completed: no # notify me by email when a job finishes
notify_failed: yes # notify me by email when a job fails
Step 3: On your workstation or on nord3v2, cd to the code directory and run:
source MODULES
Rscript split.R <path_to_your_recipe>
This will create an output directory, split your recipe into atomic recipes for independent verifications, and modify the configuration of your experiment according to the parameters in the recipe. At the end of the script, some instructions will be written in the terminal on what you need to do to start running your experiments. Follow them.
Step 4: You can and check the status of your experiment in the Autosubmit GUI. If your experiment doesn't show up at first, try disabling the "Only Active" option next to the search bar.
Please don't hesitate to ask questions if anything is unclear. Report everything (problems, success) in this issue.
Cheers,
Victòria
FYI @lpalma