Allow Cyclus runs from within Cypher - #5
Merged
Merged
Conversation
…e stuff from earlier docs now that milestone-1 is complete.
This file contains hidden or 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
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.
The initial edge of Cypher was set conservatively to being able to generate Cyclus input files, but not to run them. It was always planned to allow Cyclus runs from within Cypher, similar to how you can run OpenMC. This PR adds the necessary code to allow:
such that it should then be possible to do:
and hand the output of the simulation off to cymetric directly within the same notebook. This hopefully creates a seamless workspace experience for users, who should be able to only ever interact with Cyclus through an ipython notebook if they want.