commit 0a3a035cc794a63af63c86c0c68decfdb2d808f2 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Mon Aug 8 13:58:58 2022 -0400 Updates diff --git a/appendix.md b/appendix.md index b2b41dc..715e1a8 100644 --- a/appendix.md +++ b/appendix.md @@ -1,6 +1,9 @@ -# Appendix +--- +pagetitle: Writing the Appendix +version: 1.2 +--- -v1.1 +# Writing the Appendix An appendix is a section at the end of your main document that contains supplementary information such as figures, tables, raw data, commit dc120c6fe8b1a52f801b8b486cb86661fab977ba Author: Mark Claypool <claypool@cs.wpi.edu> Date: Fri May 20 11:48:50 2022 -0400 Updates diff --git a/appendix.md b/appendix.md index c01aeb5..b2b41dc 100644 --- a/appendix.md +++ b/appendix.md @@ -1,11 +1,15 @@ # Appendix -v1.0 +v1.1 -There are no requirements for the appendix. Instead, you put content -there that someone might want to see or it might be useful, but it is -somewhat extraneous to the report body and/or too detailed to describe -inline. +An appendix is a section at the end of your main document that +contains supplementary information such as figures, tables, raw data, +code, etc. + +There are no requirements for having an appendix. Instead, use your +judgment to content there that someone might want to see or it might +be useful, but it is somewhat extraneous to the report body and/or too +detailed to describe inline. Performance graphs you've drawn that might be interesting but you don't describe/analyze in the results are good candidates. @@ -17,7 +21,7 @@ Code (if not straightforward) that you used in your experiments (e.g., a script) perhaps. You do not have to look for stuff to put in here. Again, if you have -content that could be useful but don't describe, consider it for the +content that could be useful but do not describe, consider it for the appendix. **Tip!** If you *do* want to refer the reader to some details in the commit 29566eb1e401a758ccbf832b7723797304b470c6 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Fri Mar 25 06:17:49 2022 -0400 Updates diff --git a/appendix.md b/appendix.md index 39baca5..c01aeb5 100644 --- a/appendix.md +++ b/appendix.md @@ -1,11 +1,11 @@ # Appendix -v0.1 +v1.0 There are no requirements for the appendix. Instead, you put content -there that someone might want to see, but it is somewhat extraneous to -the report body and/or too detailed to describe inline. If you do -want to refer to it, it should probably be in the main body. +there that someone might want to see or it might be useful, but it is +somewhat extraneous to the report body and/or too detailed to describe +inline. Performance graphs you've drawn that might be interesting but you don't describe/analyze in the results are good candidates. @@ -13,8 +13,13 @@ don't describe/analyze in the results are good candidates. You might include full copies of the demographics questions and the QoE questions (if those don't appear in the methodology body). -Code (if not straightforward) that you used in your -experiments (e.g., a script) perhaps. +Code (if not straightforward) that you used in your experiments (e.g., +a script) perhaps. -You don't have to reach for stuff - again, if you have content that -could be useful but don't describe, consider it for the appendix. +You do not have to look for stuff to put in here. Again, if you have +content that could be useful but don't describe, consider it for the +appendix. + +**Tip!** If you *do* want to refer the reader to some details in the +material in the appendix, that content (at least an excerpt) should +probably be in the main report body. commit c953ec66785852640f6e91b87d121fb0e6571aa3 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Tue Apr 13 12:10:05 2021 -0400 Updates diff --git a/appendix.md b/appendix.md new file mode 100644 index 0000000..39baca5 --- /dev/null +++ b/appendix.md @@ -0,0 +1,20 @@ +# Appendix + +v0.1 + +There are no requirements for the appendix. Instead, you put content +there that someone might want to see, but it is somewhat extraneous to +the report body and/or too detailed to describe inline. If you do +want to refer to it, it should probably be in the main body. + +Performance graphs you've drawn that might be interesting but you +don't describe/analyze in the results are good candidates. + +You might include full copies of the demographics questions and the +QoE questions (if those don't appear in the methodology body). + +Code (if not straightforward) that you used in your +experiments (e.g., a script) perhaps. + +You don't have to reach for stuff - again, if you have content that +could be useful but don't describe, consider it for the appendix.