Replies: 1 comment 1 reply
-
@yw-fang: Thank you for your question. In general, the recommended approach to change settings for a given project would be to use environment variables, as noted in the settings documentation. For instance, if using a cluster, you would ensure that your SLURM script would have Or in your case, there is a simpler approach: strip the decorator. from quacc import change_settings, strip_decorator
from quacc.recipes.vasp.core import static_job
from ase.build import bulk
atoms = bulk("Cu")
my_settings = {"STORE": {"MongoStore": {"database": "mydb", "collection_name": "outputs", "username": "", "password": "", "host": "localhost", "port": 27017}}}
static_job_ = strip_decorator(static_job)
with change_settings(my_settings):
result = static_job_(atoms, kpts=[2,2,2])
print(result) Another approach would be to have multiple YAML files, and specify which YAML file you want to use using Basically, the issue you are running into is that the I will open a PR that raises a clear error if a user puts |
Beta Was this translation helpful? Give feedback.
-
Hi, all,
While we can use a ~/.quacc.yaml to set up the global settings for most calculations, is it possible to overwrite the settings for a specific project?
I tried several ways to make it (including redecorate, change_settings, etc), but all of them did not work.
Here is my .quacc.yalm used for user-worker split mode:
Now, in a specific project, I don't want to use any WORKFLOW_ENGINE. In addition, I'd like to run the quacc directly in the remote HPC and want to save the output of quacc to a particular database named "mydb"
I executed this script in the remote HPC, and it didn't run the vasp calculations, and only prints a uuid for a job:
Job(name='static_job', uuid='09853b2e-xxxx-42c5-xxxx-xxxxxxxxxx')
which indicated that the jobflow was still used.
Does anyone know how to change the settings properly? Thank you!
Beta Was this translation helpful? Give feedback.
All reactions