You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, IMO recommendations should be left for settings that optimize program execution, not are essential to function. Also, needing to set a global configuration is not ideal if you want to run dask with other configurations. You can set environment variables in your script, but doing that for something that's essential for function is also not ideal.
Dask has a configuration context manager: https://docs.dask.org/en/stable/configuration.html#dask.config.set
Would it be possible to use this in Evaluator? Alternatively, would it be possible to emit a warning or error upon seeing known bad configurations? While the Dask worker job dies on SLURM, the overall manager job continues, so it's easy to incur some wastage of computer time.
Tests
I would have looked into this further out of interest, but was a bit stumped by the tests not working. The backend tests are currently skipped because of Travis. After removing the skip, they continued not working because GH runners aren't an HPC environment, I guess (https://github.com/lilyminium/openff-evaluator/tree/lily/dask-backends). Is OpenFF interested in bringing these tests back? The Dask Jobqueue library sets up Docker images for testing.
The text was updated successfully, but these errors were encountered:
Daemon workers and dask config
I tried to set up a DaskSLURMBackend and received this error:
This is addressed by Evaluator's documentation, which recommends setting up a dask distributed configuration that switches daemons off: https://openff-evaluator.readthedocs.io/en/stable/backends/daskbackends.html#configuration
However, IMO recommendations should be left for settings that optimize program execution, not are essential to function. Also, needing to set a global configuration is not ideal if you want to run dask with other configurations. You can set environment variables in your script, but doing that for something that's essential for function is also not ideal.
Dask has a configuration context manager: https://docs.dask.org/en/stable/configuration.html#dask.config.set
Would it be possible to use this in Evaluator? Alternatively, would it be possible to emit a warning or error upon seeing known bad configurations? While the Dask worker job dies on SLURM, the overall manager job continues, so it's easy to incur some wastage of computer time.
Tests
I would have looked into this further out of interest, but was a bit stumped by the tests not working. The backend tests are currently skipped because of Travis. After removing the skip, they continued not working because GH runners aren't an HPC environment, I guess (https://github.com/lilyminium/openff-evaluator/tree/lily/dask-backends). Is OpenFF interested in bringing these tests back? The Dask Jobqueue library sets up Docker images for testing.
The text was updated successfully, but these errors were encountered: