This is a first draft of some documentation that tells the user how to use MARCS to get a file useable for STARDIS and run a STARDIS simulation with it. Make sure to keep an eye on if I misused terminology or something silly like that as I'm still new to this. lastly, right now the new documentation is just floating in a directory made specifically for it, I am unsure as to where that directory should live so that will likely need to be changed.
Also, link issues affected by this pull request by using the keywords: close, closes, closed, fix, fixes, fixed, resolve, resolves or resolved.
:pushpin: Resources
Examples, notebooks, and links to useful references.
:vertical_traffic_light: Testing
How did you test these changes?
[ ] Testing pipeline
[ ] Other method (describe)
[ ] My changes can't be tested (explain why)
:ballot_box_with_check: Checklist
[ ] I requested two reviewers for this pull request
[ ] I updated the documentation according to my changes
[ ] I built the documentation by applying the build_docs label
Note: If you are not allowed to perform any of these actions, ping (@) a contributor.
:pencil: Description
Type: :memo:
documentation
This is a first draft of some documentation that tells the user how to use MARCS to get a file useable for STARDIS and run a STARDIS simulation with it. Make sure to keep an eye on if I misused terminology or something silly like that as I'm still new to this. lastly, right now the new documentation is just floating in a directory made specifically for it, I am unsure as to where that directory should live so that will likely need to be changed.
Also, link issues affected by this pull request by using the keywords:
close
,closes
,closed
,fix
,fixes
,fixed
,resolve
,resolves
orresolved
.:pushpin: Resources
Examples, notebooks, and links to useful references.
:vertical_traffic_light: Testing
How did you test these changes?
:ballot_box_with_check: Checklist
build_docs
label