-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add mention of "model_output_dir" key in documentation; fix broken crossrefs #188
base: main
Are you sure you want to change the base?
Conversation
This will address #187
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.
This looks good to me, though I'm not sure how to rigorously check the updated markdown links without a preview. Thanks!
Luckily RTD checks the crosslinks automatically (they were broken earlier because I was not familiar with the system and assumed that it was always just screaming at me about something trivial). The markdown preview is always going to be under the information from the checks in this repo. Here's the link: https://hubdocs--188.org.readthedocs.build/en/188/ |
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.
Hi @Zhian, this looks good to me. I must admit I haven't gotten into this much detail in the manuscript, but this is good to know.
One very minor naming change requested for consistency throughout docs but overall looks great! Thanks @zkamvar ! |
Co-authored-by: Anna Krystalli <[email protected]>
This adds a sidetone about "model_output_dir" in two places that mention
model-output
to fix #187Requesting a review from @mmkerr because she's working on the manuscript and I want to make sure this is accurate.
Also requesting a review from @matthewcornell who requested the change and @annakrystalli who knows the most about this specification.
As a side note, I would have linked directly to the admin.json section in the sidenote, but Sphinx was deciding to be difficult about it:
Sphinx being annoying
The error log is as follows. I'm not going to report it because I don't want to go through the process of creating a reproducible example of a sphinx site and I don't want to get yelled at for giving the maintainers a whole-ass repository.