Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • CNMS_Computing_Resources CNMS_Computing_Resources
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CNMS
  • CNMS_Computing_ResourcesCNMS_Computing_Resources
  • Wiki
  • PBS Tricks

Last edited by Doak, Peter W Mar 30, 2017
Page history

PBS Tricks

PBS Tricks

Multiple mpirun's in one pbs job

For an example of multiple mpirun's in a single PBS job see: VASP example

Chaining pbs jobs

This is actually a pretty good primer on job chaining techniques. https://www.nics.tennessee.edu/computing-resources/running-jobs/job-chaining

If you combine the above two you can run many long trajectories or relaxations via backfilling without fragmenting the hpc environment and making highly parallel jobs difficult to launch.

Clone repository
  • ABINIT
  • BASH
  • Cades
  • ESPRESSO
  • Git Best Practices
  • LAMMPS
  • Learning Resources
  • Metis
  • Monitoring Codes
  • Nersc
  • OIC
  • OLCF
  • OSX
  • Outside_Users
  • PBS Tricks
View All Pages