Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiple cerise specialisations from same lie_md #17

Open
marcvdijk opened this issue Feb 12, 2019 · 1 comment
Open

multiple cerise specialisations from same lie_md #17

marcvdijk opened this issue Feb 12, 2019 · 1 comment
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@marcvdijk
Copy link
Member

When running a LIE workflow with MD jobs requesting to run go GT-GPU nodes followed by running another LIE workflow in parallel requesting regular GT nodes for MD, the latter workflow will use the GPU specialisation instead.

Seems that lie_md does not keep track of different specialisations in parallel or at all?

@marcvdijk marcvdijk added enhancement New feature or request question Further information is requested labels Feb 12, 2019
@marcvdijk marcvdijk added bug Something isn't working and removed question Further information is requested labels Feb 13, 2019
@marcvdijk
Copy link
Member Author

Changing the issue status to "bug" as it seems that lie_md is not keeping track of different types of HPC specialisations but just takes whatever is around.
That means that even when taking MDStudio offline, the docker specialisation is still running (perhaps also something to change) and when MDStudio is launched again that specialisation will be used again even if the workflow defines a different one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants