Changes between Version 68 and Version 69 of cypress/using
- Timestamp:
- 12/12/22 11:07:59 (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
cypress/using
v68 v69 419 419 #SBATCH --time=24:00:00 # WallTime 420 420 #SBATCH --nodes=1 # Number of Nodes 421 #SBATCH --ntasks-per-node= 1 # Number of tasks (MPI presseces)422 #SBATCH --cpus-per-task= 20 # Number of processors per task OpenMP threads()421 #SBATCH --ntasks-per-node=20 # Number of tasks 422 #SBATCH --cpus-per-task=1 # Number of cores per task 423 423 424 424 # Our custom function … … 427 427 sleep 1 428 428 } 429 # For loop 20times429 # For loop $SLURM_NTASKS_PER_NODE times 430 430 date 431 for i in {1..20}431 for i in $(seq $SLURM_NTASKS_PER_NODE) 432 432 do 433 433 cust_func $i & # Put a function in the background … … 479 479 480 480 Note the prompt, "cypress01-100", in the above session. It is your interactive compute-node prompt. You can load modules, compile codes and test codes. 481 `idev` transfers the environmental variables to computing node. Therefore, if you have loaded some modules on the login node, you don't have to load the same module again.481 `idev` transfers the environmental variables to the computing node. Therefore, if you have loaded some modules on the login node, you don't have to load the same module again. 482 482 483 483 ==== How to exit `idev` ==== … … 498 498 ==== Options ==== 499 499 500 By default only a single node is requested for 60 minutes. However, you can change the limits with command line options, using syntax similar to the request specifications used in a job script.500 By default, only a single node is requested for 60 minutes. However, you can change the limits with command line options, using syntax similar to the request specifications used in a job script. 501 501 The syntax is conveniently described in the `idev` help display: 502 502