Gaussian QM Run Input Files
Category Paths
Follow one of these paths in the Orion user interface, to find the floe.
Solution-based/Small Molecule Lead-opt/QM Analysis
Task-based/Quantum Mechanics
Role-based/Computational Chemist
Product-based/Quantum Mechanics/Gaussian
Description
Deprecated In a recent Orion release it became possible to run parallel cubes for an extended time. This makes it preferred to use the Gaussian QM Parallel Run Input Files which takes full advantage of the Orion scheduler to run all calculations in parallel. Long running calculations can now be run in parallel cubes making this serial cube based Floe unnecessary. Therefore, this Floe will be removed soon.
Important Note that a status of “Success” in the Orion UI only indicates the job is complete. Check the output of the floe to see how many Gaussian calculations completed successfully. Pay careful attention to which output files are generated. If there is a failure output file, check the Failure Report in the Floe Report tab to see how many calculations failed. To see examples of Gaussian calculations which succeed and fail, check out the the Gaussian Orion Module Tutorials.
Run any Gaussian input file(s). Output for all calculations is saved into a single archive (tar) file. The goal of this floe is to allow Orion to be used as the computational engine for any Gaussian calculation. For help creating Gaussian input files, see Gaussian documentation here: https://gaussian.com/input/
Input Files Input files to this floe should be Gaussian input files (with extension .com or .gjf) or TAR or ZIP archived directories. For archived directories, if a subdirectory has multiple input files, they will each be moved into a separate subdirectory. For example, if an input directory had two input files (calc_1.com and calc_2.com), the output file would have two output directories (calc_1 and calc_2) with all outputs from each calculation stored in the respective subdirectory.
To maintain the same directory structure for input and output, make sure there is only one input file in each subdirectory. In all cases, the Gaussian input file should have extensions .com or .gjf. Calculation files with any other extension will fail this floe. If a checkpoint file (or other formats) is in the same input directory, they can be used for the calculation as well.
Gaussian Calculation The Hardware Requirements set for this floe attempt to be reasonable for calculations with drug-like molecules. However, if using expensive methods or large basis sets, it is recommended that a benchmark calculation is performed to check. Metrics are enabled for the Run Gaussian Inputs Cubes so they can be monitored while a calculation is running.
Saving Output The output directory for all calculations is saved as a tar file. If the file extension provided is not recognized, it will be replaced with ‘.tar’. Currently, tar files with no compression or gzip, bzip2, or lzma compression are supported. If the size of this archive file exceeds the Max Gaussian Output File Size (default 1,000 MB), then a second output file will be created with the same name followed by a number.
Whether or not the Gaussian calculation succeeds, all output from the job will be saved for post processing. The file from the ‘Successful Calculations Tar Archive File’ parameter will contain directories for all successful calculations. The file from the ‘Failed Calculation Tar Archive File’ parameter will contain a directory for any failed calculations. To understand these failures, look at the Orion failure report and the log file in each directory.
Promoted Parameters
Title in user interface (promoted name)
Inputs
Gaussian Input File(s) (in): Gaussian input files (.com or .gjf) or archived directory with multiple input files. Zip files or Tar files with gzip, bzip2, lzma, or no compression are currently supported. Any additional input files (i.e., checkpoint files) should be in the same subdirectory as their respective Gaussian file.
Required
Type: file_in
Outputs
Successful Calculations Tar Archive File (out): Title for the output archive file for successful calculations.
Required
Type: file_out
Default: Gaussian_output.tar
Failed Calculation Tar Archive File (failure): Title for the output archive file for failed calculations.
Required
Type: file_out
Default: Gaussian_failures.tar
Max Gaussian Output File Size (MB) (gau_max_directory_size): Specify a maximum output file size. When the file size is exceeded a new tar file will be created. Until all of the output is saved. When multiple files are being created an increment will automatically be added.
Type: decimal
Default: 1000
Save Log files (store_log_file): Save output log files for all calculations, they are always saved for failed calculations.
Type: boolean
Default: True
Choices: [True, False]
Report Name for Log Files (gau_log_report_name): Gaussian log files for the calculation are saved to a floe report. This allows Gaussian log files to be viewed on Orion before downloading results. Log files are saved for all failures and optionally saved for successful calculations if the Store Log Files above is turned On.
Type: string
Default: Gaussian Log File Report
Hardware Requirements for Gaussian Calculation
Gaussian # Threads (gaussian_nthreads): Number of CPUs for Gaussian calculation.
Type: integer
Default: 8
Gaussian Memory (gaussian_memory): Memory for Gaussian calculations in MBs.
Type: decimal
Default: 14400
Gaussian Disk Space (gaussian_disk_space): Temporary disk space (in MB) required for your calculation.
Type: decimal
Default: 25600
Instance Type (gaussian_instance_type): ADVANCED: This parameter is to specify the specific AWS instance type for the Gaussian calculation to run on. Orion has a scheduler which will automatically find the best instance for the other hardware requirements. You should not specify this parameter unless you are absolutely sure you want to limit instance type. Since Gaussian Calculations are performed on many serial Cubes this parameter is promoted to make sure it is set on all of the copies of the Gaussian calculation Cube.
Type: string