Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • E ear_learning
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • EAR_teamEAR_team
  • ear_learning
  • Wiki
  • 3 ˗ Kernels test

3 ˗ Kernels test · Changes

Page history
Updated 3 ˗ Kernels test (markdown) authored Dec 12, 2019 by xjgomez's avatar xjgomez
Show whitespace changes
Inline Side-by-side
3-˗-Kernels-test.md
View page @ 76d88e38
...@@ -4,7 +4,7 @@ The test script launches all the kernels one time to check if its elapsed times ...@@ -4,7 +4,7 @@ The test script launches all the kernels one time to check if its elapsed times
1) To launch the script, SLURM will be used, then it is required the `sbatch` and the commands `srun` or `mpirun` bootstraping SLURM. So, open the script `scripts/learning/helpers/kernels_executor.sh` and look at the function `launching()`. Check if the SLURM command is correct to run the test in your super computer. These are two examples of the `srun` and `mpirun` commands for a node of 40 CPUs: 1) To launch the script, SLURM will be used, then it is required the `sbatch` and the commands `srun` or `mpirun` bootstraping SLURM. So, open the script `scripts/learning/helpers/kernels_executor.sh` and look at the function `launching()`. Check if the SLURM command is correct to run the test in your super computer. These are two examples of the `srun` and `mpirun` commands for a node of 40 CPUs:
`srun -N 1 -n 40 -J "bt-mz" -w node1001 --ear-policy=MONITORING_ONLY --ear-learning=1 /installation.path/bin/kernels/bt-mz.C.40` `srun -N 1 -n 40 -J "bt-mz" -w node1001 --ear-verbose=1 --ear-learning=1 /installation.path/bin/kernels/bt-mz.C.40`
`mpirun -n 40 -bootstrap slurm -bootstrap-exec-args="-J 'bt-mz' -w node1001 --ear-verbose=1 --ear-learning=1 /installation.path/bin/kernels/bt-mz.C.40` `mpirun -n 40 -bootstrap slurm -bootstrap-exec-args="-J 'bt-mz' -w node1001 --ear-verbose=1 --ear-learning=1 /installation.path/bin/kernels/bt-mz.C.40`
......
Clone repository
  • 1 ˗ Kernels compile
  • 2 ˗ Nodes lists guidelines
  • 3 ˗ Kernels test
  • 4 ˗ Kernels launch
  • 5 ˗ Coefficients compute
  • Home