|
| 1 | +# Gaussian |
| 2 | + |
| 3 | +:::{important} |
| 4 | +Access to Gaussian requires permission. Please open a help ticket by emailing |
| 5 | +[help@smu.edu with |
| 6 | +"[HPC]"](mailto:help@smu.edu?subject=[HPC]%20Gaussian%20Access%20Request) |
| 7 | +in the subject line. |
| 8 | +::: |
| 9 | + |
| 10 | +**Gaussian** Gaussian series of electronic structure programs, used by chemists, chemical engineers, biochemists, physicists and other scientists worldwide. |
| 11 | + |
| 12 | +**Gaussian homepage**: [gaussian.com/](https://gaussian.com/) |
| 13 | + |
| 14 | +**Official Gaussian Manual**: [gaussian.com/man/](https://gaussian.com/man/) |
| 15 | + |
| 16 | +:::{seealso} |
| 17 | +For examples and tips on submitting jobs, see [our SLURM documentation](tutorials:slurm) and [Best Practices for Jobs](tutorials:slurm:best_practices) |
| 18 | + |
| 19 | +For compute resources, see [HPC Queues](about:queues) |
| 20 | +::: |
| 21 | + |
| 22 | +<!-- ## Using Gaussian on the SuperPod |
| 23 | +
|
| 24 | +Files used in the example are available: |
| 25 | +
|
| 26 | + - [on github](https://github.com/SouthernMethodistUniversity/hpc_docs/tree/main/docs/examples/gaussian) |
| 27 | + - on the SuperPod at `/hpc/mp/examples/gaussian/` |
| 28 | +
|
| 29 | +### Example submission script |
| 30 | +
|
| 31 | +The following job script can be submitted using `sbatch gaussian_gpu_example.sbatch`. |
| 32 | +
|
| 33 | +```{literalinclude} gaussian_gpu_example.sbatch |
| 34 | +--- |
| 35 | +language: bash |
| 36 | +linenos: true |
| 37 | +--- |
| 38 | +``` --> |
| 39 | + |
| 40 | +## Using Gaussian on M3 |
| 41 | + |
| 42 | +Files used in the example are available: |
| 43 | + |
| 44 | + - [on github](https://github.com/SouthernMethodistUniversity/hpc_docs/tree/main/docs/examples/gaussian) |
| 45 | + - on M3 at `/hpc/m3/examples/gaussian/` |
| 46 | + |
| 47 | +### Example submission script |
| 48 | + |
| 49 | +The following job script can be submitted using `sbatch guassian_cpu_example.sbatch`. |
| 50 | + |
| 51 | +This example will run in about 10 seconds and use less that `1GB` of memory. |
| 52 | +In general, more complicated simulations will take much longer and should typically |
| 53 | +use more cores and memory. Note, we know this from running the job. |
| 54 | +It is always a good idea to review the resources your jobs use |
| 55 | +and adjust future jobs to more accurately request resources. |
| 56 | + |
| 57 | +This uses the `dev` |
| 58 | +queue which has a 2 hour time limit. |
| 59 | +In general, the `dev` queue should only be used for testing code and running interactive |
| 60 | +sessions. |
| 61 | +Most normal jobs should be submitted to the standard queues such as `standard-s` where |
| 62 | +longer runtimes are allowed. |
| 63 | + |
| 64 | +This example also writes output to `$SCRATCH`. |
| 65 | +`$SCRATCH` is a high performance file system designed to be used for temporary |
| 66 | +job files and data. |
| 67 | +After a job has finished running, any data you need to keep should be moved to |
| 68 | +a project directory or your $HOME directory. |
| 69 | +**Files in `SCRATCH` are subject to a 60 day purge policy where files older than 60 days |
| 70 | +may be automatically deleted without warning.** |
| 71 | + |
| 72 | +:::{note} |
| 73 | +This job script will not run without modification. In particular, you must change |
| 74 | +the account from `peruna_project_0001` to the account name for an allocation you |
| 75 | +have access to. |
| 76 | +::: |
| 77 | + |
| 78 | +```{literalinclude} gaussian_cpu_example.sbatch |
| 79 | +--- |
| 80 | +language: bash |
| 81 | +linenos: true |
| 82 | +--- |
| 83 | +``` |
| 84 | + |
0 commit comments