This page was translated by an AI (LLM) with a cursory human check and is awaiting full review.
Transition between two projects
This page contains useful information for Jean Zay users who wish to transfer their workflow from one project to another. This documentation is based on the multi-project account management tools.
To perform this transition, the user's login must be attached to both projects concerned: the initial project and the new project (respectively called old and new in the example below).
The return of the command idrproj then contains the following information:
idrproj
Available projects:------------------- old (123456) [default][active] new (654321)Both projects must coexist throughout the transition period. You must ensure that the administrative procedures for opening the new project and attaching your login to this project are completed before the initial project expires. For your information, once the expiration date has passed, you will no longer have access to the computing hours of the initial project. However, the data contained in the disk spaces associated with the initial project are retained and accessible for a further six months.
Your HOME directory is personal and unique. Therefore, you do not need to transfer the data it contains.
However, if you have created symbolic links in your HOME directory pointing to the disk spaces of the initial project, you must modify them to point to the disk spaces of the new project and not forget to transfer the target directories (see below).
Modifying the default project
To modify your default project, you must use the command idrproj -d <new default project>:
idrproj -d newPassword:Default project changed to newUpon the next connection, the return of the command idrproj will be:
idrproj
Available projects:------------------- old (123456) new (654321) [default][active]After this operation, all default behaviours for connection, environment, job submission and accounting are redirected to your new project.
Data transfer
During the transition period from one project to another, the disk spaces of both projects coexist. To designate these disk spaces unambiguously, it is advisable to use the corresponding environment variables prefixed with the project name (old_ or new_ in the example):
idrenv...export new_ALL_CCFRSCRATCH=/...scratchpath.../new/commun; # $SCRATCH commun du projet newexport new_ALL_CCFRSTORE=/...storepath.../new/commun; # $STORE commun du projet newexport new_ALL_CCFRWORK=/...workpath.../new/commun; # $WORK commun du projet newexport new_CCFRSCRATCH=/...scratchpath.../new/user; # $SCRATCH du projet newexport new_CCFRSTORE=/...storepath.../new/user; # $STORE du projet newexport new_CCFRWORK=/...workpath.../new/user; # $WORK du projet newexport old_ALL_CCFRSCRATCH=/...scratchpath.../old/commun; # $SCRATCH commun du projet oldexport old_ALL_CCFRSTORE=/...storepath.../old/commun; # $STORE commun du projet oldexport old_ALL_CCFRWORK=/...workpath.../old/commun; # $WORK commun du projet oldexport old_CCFRSCRATCH=/...scratchpath.../old/user; # $SCRATCH du projet oldexport old_CCFRSTORE=/...storepath.../old/user; # $STORE du projet oldexport old_CCFRWORK=/...workpath.../old/user; # $WORK du projet old...Data can thus be transferred from one space to another in the usual way. For example:
$ cp -rp $old_CCFRWORK/mydata $new_CCFRWORK/.You can also run your computations using input data stored in the initial disk spaces and direct the outputs to the new disk spaces.
Accounting
As long as the initial project has not expired, you can request that the computing hours be deducted from the allocation of the initial project or the new project when submitting a job, independently of the disk spaces in which you are working.
The Slurm option to specify in your Slurm scripts or during a salloc, srun or sbatch is:
- for a job launched on the CPU partition:
--account=new@cpuor--account=old@cpu - for a job launched on the GPU partition (here V100):
--account=new@v100or--account=old@v100