You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since moving to Submittable, Amherst Thesis Guidelinesthe college no longer requires separate signed copyright page nor the binding format, but the Statistics Honors Thesis Regulations still list these. Do we want to maintain binding margins (1.5in inner, 1in otherwise) or move to just 1in margins all around? If the latter, I can include instructions for easily switching to binding format.
Cannot list all code within document in an appendix, but can list all code within each qmd files. Some potential options:
Include all source code scripts (e.g., all .R files) in appendix.
Include all code used in chapter at the end of each chapter (each .qmd has to be self-contained anyway).
Link thesis GitHub repo in a reproducibility statement in appendix.
Some combination of the above.
What should be the default behavior and advice around displaying code chunks? Currently #| echo: false.
What should be the default behavior and advice around displaying code messages and warnings? Currently #| message: false and #| warning: false.
Any preference around code background? Shaded box or not? Currently shaded.
Any preference around code line numbering? Include or exclude? Currently included.
Formatting decisions to discuss
Since moving to Submittable, Amherst Thesis Guidelinesthe college no longer requires separate signed copyright page nor the binding format, but the Statistics Honors Thesis Regulations still list these. Do we want to maintain binding margins (1.5in inner, 1in otherwise) or move to just 1in margins all around? If the latter, I can include instructions for easily switching to binding format.
Cannot list all code within document in an appendix, but can list all code within each qmd files. Some potential options:
.Rfiles) in appendix..qmdhas to be self-contained anyway).What should be the default behavior and advice around displaying code chunks? Currently
#| echo: false.What should be the default behavior and advice around displaying code messages and warnings? Currently
#| message: falseand#| warning: false.Any preference around code background? Shaded box or not? Currently shaded.
Any preference around code line numbering? Include or exclude? Currently included.