-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
8 changed files
with
302 additions
and
39 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
FROM molssi/mamba141 | ||
|
||
COPY ./environment.yml /root/environment.yml | ||
|
||
RUN mamba env update -f /root/environment.yml | ||
|
||
WORKDIR /home | ||
ENTRYPOINT ["packmol"] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
name: base | ||
channels: | ||
- conda-forge | ||
dependencies: | ||
- python | ||
# Executables, etc. | ||
- packmol==20.2.2 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,6 @@ | ||
[packmol-step] | ||
# Information about where/how the executables are installed | ||
# installation may be 'user', 'conda' or 'module'. If a module is | ||
# specified it will be loaded and those executables used. In this | ||
# case, any path specified using -path will be ignored. | ||
|
||
installation = | ||
conda-environment = | ||
modules = | ||
# The level of logging for the Packmol Step | ||
|
||
# The path to the executable. Can be empty or not present, in which | ||
# case the default PATH is used. If a path is given, packmol | ||
# from this location will be used. | ||
# | ||
# Ignored if a module is used. The default is to use the PATH | ||
# environment variable. | ||
|
||
packmol-path = | ||
# log-level WARNING | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
# Configuration options for how to run Packmol | ||
|
||
[docker] | ||
# The code to use. This may maybe more than just the name of the code, and variables in | ||
# braces {} will be expanded. For example: | ||
# code = mpiexec -np {NTASKS} lmp_mpi | ||
# would expand {NTASKS} to the number of tasks and run the command | ||
|
||
code = packmol | ||
|
||
# The name and location of the Docker container to use, optionally with the version | ||
|
||
container = ghcr.io/molssi-seamm/seamm-packmol:{version} | ||
|
||
# In addition, you can specify the platform to use. This is useful on e.g. Macs with | ||
# app silicon (M1, M3...) where the default platform is linux/arm64 but some containers | ||
# are only available for linux/amd64. | ||
|
||
# platform = linux/amd64 | ||
|
||
[local] | ||
# The type of local installation to use. Options are: | ||
# conda: Use a conda environment | ||
# modules: Use the modules system | ||
# local: Use a local installation | ||
# docker: Use a Docker container | ||
# By default SEAMM installs Packmol using conda. | ||
|
||
installation = conda | ||
|
||
# The command line to use, which should start with the executable followed by any options. | ||
# Variables in braces {} will be expanded. For example: | ||
# | ||
# code = mpiexec -np {NTASKS} lmp_mpi | ||
# | ||
# would expand {NTASKS} to the number of tasks and run the command. | ||
# For a 'local' installation, the command line should include the full path to the | ||
# executable or it should be in the path. | ||
|
||
code = packmol | ||
|
||
######################### conda section ############################ | ||
# The full path to the conda executable: | ||
|
||
# conda = | ||
|
||
# The Conda environment to use. This is either the name or full path. | ||
|
||
# conda-environment = seamm-packmol | ||
|
||
######################### modules section ############################ | ||
# The modules to load to run Packmol, as a list of strings. | ||
# For example, to load the modules packmol and openmpi, you would use: | ||
# modules = packmol openmpi | ||
|
||
# modules = | ||
|
||
######################### local section ############################ | ||
# The full path to the Packmol executable should be in the 'code' option. | ||
|
||
######################### docker section ############################ | ||
# The name and location of the Docker container to use, optionally with the version. | ||
# {version} will be expanded to the version of the plug-in. | ||
|
||
# container = ghcr.io/molssi-seamm/seamm-packmol:{version} | ||
|
||
# In addition, you can specify the platform to use. This is useful on e.g. Macs with | ||
# app silicon (M1, M3...) where the default platform is linux/arm64 but some containers | ||
# are only available for linux/amd64. | ||
|
||
# platform = linux/amd64 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.