Remote execution of scripts #95
Draft
Conversation
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
At the moment a code is automatically created from the script file. This works for local execution since the script is available on the computer. For remote execution the script is not available and result into an error. To copy the script over to the remote machine one could specify the file as remote data with symlink to false. This might be limiting since we want to support remote data that is symlinked in the future. One solution would be to create a `PortableCode`, but we established in meetings that this might be too limiting as we sometimes want to only use a single script without the folder. We the approach to define the bash command and add the script as argument. This is also limiting because one cannot support other scripts than bash. A different solution has to be found.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the moment a code is automatically created from the script file. This works for local execution since the script is available on the computer. For remote execution the script is not available and result into an error.
To copy the script over to the remote machine one could specify the file as remote data with symlink to false. This might be limiting since we want to support remote data that is symlinked in the future.
One solution would be to create a
PortableCode, but we established in meetings that this might be too limiting as we sometimes want to only use a single script without the folder.This PR takes tthe approach to define the bash command in Aiida and add the script as argument. This is also limiting because one cannot support other scripts than bash. A different solution has to be found.