Example using "dragon" start method #555
Open
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
|
I'm still not sure where the best place to add an example would be. The Dragon documentation would be one option (with a link from the Cubed documentation and examples). Or it could go here, but with the script named @TomNicholas you've been trying out Dragon so perhaps you have thoughts? |
|
Thinking about this more, it should be possible to add a export CUBED_CONFIG=$(pwd)/dragon/cubed.yaml
python add-asarray.pyThis would make it just like the other executors and allow any of the examples to be run on Dragon. |
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.
In discussions with Tom and Tom, it was unclear where this example involving the use of the
"dragon"start method should land. This PR is intended to help further those discussions and ensure we do not lose track of this working example.This PR is dependent upon PR #554 and is not intended to be merged independent of that PR.