... | ... | @@ -19,7 +19,7 @@ _As of June 2021 the tool has only been tested in MareNostrum4 experiments. It s |
|
|
|
|
|
Before starting the migration, the following action is recommended:
|
|
|
|
|
|
- `chmod -R g+w /gpfs/projects/bsc32/repository/exp/${EXPID}`
|
|
|
- `chmod -R g+rw /gpfs/projects/bsc32/repository/exp/${EXPID}`
|
|
|
|
|
|
Also, create a `TEMP_DIR` that both accounts (the one offering the experiment and the one picking it) have access to. For example, in MN4 it is usually convenient to create it under `/gpfs/scratch/bsc32/${bsc32-user}`
|
|
|
|
... | ... | @@ -27,11 +27,11 @@ Also, create a `TEMP_DIR` that both accounts (the one offering the experiment an |
|
|
|
|
|
Also, for **Auto-EC-Earth** and **Auto-CALIOPE** experiments
|
|
|
|
|
|
- `chmod -R g+w /esarchive/exp/${MODEL}/${EXPID}`
|
|
|
- `chmod -R g+rw /esarchive/exp/${MODEL}/${EXPID}`
|
|
|
|
|
|
In case of migration from res to bsc32, use dt machine of your res account:
|
|
|
|
|
|
- `chmod -R g+w /gpfs/archive/bsc32/esarchive/exp/${MODEL}/${EXPID}`
|
|
|
- `chmod -R g+rw /gpfs/archive/bsc32/esarchive/exp/${MODEL}/${EXPID}`
|
|
|
|
|
|
# Configure your experiment for the migration
|
|
|
|
... | ... | @@ -101,6 +101,9 @@ There are two modes of running `autosubmit migrate`, both of them consist of a t |
|
|
* * (User-Target) `autosubmit migrate <expid> -p --onlyremote`
|
|
|
|
|
|
|
|
|
`-o` moves all data from `$scratch/$original_project/$original_user/$expid` to `$tmp_dir/$expid` and `-p` transfers all data `$tmp_dir/$expid` to `$scratch/$project_to/$user_to/$expid`
|
|
|
|
|
|
|
|
|
# Tests done
|
|
|
|
|
|
The refactored tool was successfully tested with three **Auto-EC-Earth** and one **Auto-MONARCH** test experiments.
|
... | ... | |