Add in Recipe Update functionality to EVER #17
Merged
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.
This PR adds the lowest level fidelity case we envisioned for EVER (something the Cycamore Reactor already does), changing the recipe at specific times. As outlined in #10
This PR creates the header, source, and test files for EVER in this repo. It documents the functionality in the
EVER/README.md
, and adds a simple test scenario comparing to the Cycamore Reactor with an analysis notebook based on baseline.Warning
This PR does not add the functionality to build the archetype (currently the workflow is you add the files to cycamore and build them there. An issue will be created before this PR is merged to discuss/address that.
Issue #18 has been created, and PRs #23 and #24 have half addressed it. There is still no functionality to build the archetype here in NEAR, but there is now an install script that copies it over and automatically builds cycamore with the new archetype that does work.