-
Notifications
You must be signed in to change notification settings - Fork 26
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
update GlassBR to generate output requirement
- Loading branch information
Showing
19 changed files
with
413 additions
and
118 deletions.
There are no files selected for viewing
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
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
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
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
c3f57fd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also noticed that GlassBR, in addition to the main output requirement, also has the requirement to output the values that were input and the values for assigned constants:
Should these outputs be wrapped into the generated output, or should an issue be opened to potentially generate this requirement as well? Is this a requirement we should be adding to all our examples? @smiths (I personally think this would be a low priority change)
c3f57fd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@samm82 it is a common, but by no means universal, practice in research software to output the inputs as part of the outputs. (The two outputs here are different, so we don't have a recursive statement.) 😄 The idea is for easy provenance/reproducibility. If someone is looking at their calculated outputs and they wonder where they came from, the information that is needed to reproduce the results is readily available.
Eventually I would see this as an option for users of Drasil. They could select to "output the inputs" if they want to. There is no compelling reason to force this change through all of our examples. It wouldn't be wrong, but it also wouldn't be worth the effort. It would also imply that this is something that should always be done. It would be better to have the flexibility to do it, but not to force it for every current and future example.