commit 9b7330c5f435a7c28724e2d93a9143c76a9beb91 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Mon Aug 15 07:17:55 2022 -0400 Updates diff --git a/abstract.md b/abstract.md index 92f61cb..f9e524e 100644 --- a/abstract.md +++ b/abstract.md @@ -24,13 +24,13 @@ Typically, it will have (1-2 sentences of each): The abstract is the **most important** paragraph in your entire report. It is the one people will read to decide if they want to -bother reading the rest of the document. +bother reading the rest of the document. Generally, your abstract should not have figures. -Note: WPI' online system limits the number of characters to 800 for -the abstract. This is to fit in the constrained space of an academic -transcript. +Note: WPI's online system limits the number of characters to 800 +(about 120 words) for the abstract. This is to fit in the constrained +space of an academic transcript. So, prepare *two* versions: commit 0a3a035cc794a63af63c86c0c68decfdb2d808f2 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Mon Aug 8 13:58:58 2022 -0400 Updates diff --git a/abstract.md b/abstract.md index fde295f..92f61cb 100644 --- a/abstract.md +++ b/abstract.md @@ -1,6 +1,9 @@ -# Abstract Writing Guidelines +--- +pagetitle: Writing the Abstract +version: 1.4 +--- -v1.3 +# Writing the Abstract The abstract should describe (abstract) the entire report. commit 27469b4b69803e1877ac1585bb185b85a38d8135 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Wed Jan 26 08:08:45 2022 -0500 Updates diff --git a/abstract.md b/abstract.md index d3a7c4e..fde295f 100644 --- a/abstract.md +++ b/abstract.md @@ -1,6 +1,6 @@ # Abstract Writing Guidelines -v1.2 +v1.3 The abstract should describe (abstract) the entire report. @@ -23,9 +23,11 @@ The abstract is the **most important** paragraph in your entire report. It is the one people will read to decide if they want to bother reading the rest of the document. -Note: the online system will limit the number of characters to 800 -for you abstract. This is to fit in the constrained space of your -transcript. Also, your abstract should not have figures. +Generally, your abstract should not have figures. + +Note: WPI' online system limits the number of characters to 800 for +the abstract. This is to fit in the constrained space of an academic +transcript. So, prepare *two* versions: @@ -33,9 +35,8 @@ So, prepare *two* versions: Do this first. This is the one that goes into your report document. -After the above version has been iterated on and finalized, -and if your full version is over 800 characters, then -prepare: +After the above version has been iterated on and finalized, and if +your full version is over 800 characters, then prepare: 2. The short version, one that is 800 or fewer characters. Do this by using the full one and carefully cutting, preserving as much of the commit 13647cf9078d66b1182de2b31c5fbd3f4fbedc0c Author: Mark Claypool <claypool@cs.wpi.edu> Date: Fri Sep 18 09:12:35 2020 -0400 Updates diff --git a/abstract.md b/abstract.md index 262ce77..d3a7c4e 100644 --- a/abstract.md +++ b/abstract.md @@ -1,6 +1,6 @@ # Abstract Writing Guidelines -v1.1 +v1.2 The abstract should describe (abstract) the entire report. @@ -25,7 +25,7 @@ bother reading the rest of the document. Note: the online system will limit the number of characters to 800 for you abstract. This is to fit in the constrained space of your -transcript. +transcript. Also, your abstract should not have figures. So, prepare *two* versions: commit adb9bdbbda09e0c5d86f168072609acd2a2236dd Author: Mark Claypool <claypool@cs.wpi.edu> Date: Wed Feb 27 00:02:38 2019 -0500 Updates diff --git a/abstract.md b/abstract.md index af31959..262ce77 100644 --- a/abstract.md +++ b/abstract.md @@ -1,6 +1,6 @@ # Abstract Writing Guidelines -v1.0 +v1.1 The abstract should describe (abstract) the entire report. @@ -33,7 +33,10 @@ So, prepare *two* versions: Do this first. This is the one that goes into your report document. -2. If your full version is over 800 characters, prepare one that is -800 or fewer characters. Do this by using the full one and carefully -cutting, preserving as much of the original flow and meaning as -possible, until it is down to size. +After the above version has been iterated on and finalized, +and if your full version is over 800 characters, then +prepare: + +2. The short version, one that is 800 or fewer characters. Do this by +using the full one and carefully cutting, preserving as much of the +original flow and meaning as possible, until it is down to size. commit e5cfe6bf704f9f36d0c26fae9e94d6228e50907b Author: Mark Claypool <claypool@cs.wpi.edu> Date: Tue Feb 26 12:53:28 2019 -0500 Updates diff --git a/abstract.md b/abstract.md new file mode 100644 index 0000000..af31959 --- /dev/null +++ b/abstract.md @@ -0,0 +1,39 @@ +# Abstract Writing Guidelines + +v1.0 + +The abstract should describe (abstract) the entire report. + +Typically, it will have (1-2 sentences of each): + ++ Broad topic (e.g., "The Internet is big ...") + ++ Narrower domain (e.g., "Local area networks are smaller ...") + ++ Problem statement (e.g., "WPI's network has problems ...") + ++ Project (e.g., "Our project was to fix WPI's network by ...") + ++ Methods (e.g., "We did steps XYZ ...") + ++ Results (e.g., "Based on our experiments/methods/analysis we found + ABC...") + +The abstract is the **most important** paragraph in your entire +report. It is the one people will read to decide if they want to +bother reading the rest of the document. + +Note: the online system will limit the number of characters to 800 +for you abstract. This is to fit in the constrained space of your +transcript. + +So, prepare *two* versions: + +1. The long, full version, not worrying about the 800 character limit. +Do this first. This is the one that goes into your report +document. + +2. If your full version is over 800 characters, prepare one that is +800 or fewer characters. Do this by using the full one and carefully +cutting, preserving as much of the original flow and meaning as +possible, until it is down to size.