Ch6' Graphs, figures, and tables Writing for Informatics

1
Ch6. Graphs, figures, and tables Writing for
Informatics

• 2008. 5. 2
• In-Bon Kuh
• GNU OSLab.

2
Contents

• Ch6. Graphs, figures, and tables
• Graphs
• Visualization of results
• Diagrams
• Tables
• Captions and labels
• Axes, labels, and headings

3
Tables

• Focusing on
• the properties of each of a series of datasets
• data where the exact values are important
• Logical hierarchical structure
• heading at the top, label or stub at the left
• separated by double/single lines, or white space
• spanning several columns and rows
• same kind or about the same thing below a column
  head
• properties of that label to the right of a row
  label

4

• To be OPEN and UNCLUTTERED table
• dont have too many horizontal or vertical rules
• have rules between groups of rows and rarely
  between groups of columns
• dont make tables too dense
• be selective about the information among lots of
  items
• dont leave items as blank
• put in a dash and explain somewhere else

5
X
Table 6. Statistics of text collections used in
experiments.
6
?
Table 6. Statistics of text collections used in
experiments.
7
?
TABLE 2.1. Impact on performance (processing
time and effectiveness) of varying each of the
three parameters in turn, for both data sets.
Default parameter values are shown in
parentheses. Note that p 100,000 is not
meaningful for the data set SINGLE.
8
X
TABLE 11. Resources used during compression and
indexing. Only the vocabulary is constructed in
the first pass the other structures are built in
the second pass.
9
?
TABLE 11. Resources used during compression and
indexing. Only the vocabulary is constructed in
the first pass the other structures are built in
the second pass.
10
Captions and Labels

• Be informative captions
• describe the figures major elements not like in
  common sense in computer science paper
• explain important details
• expand abbreviations or notation in heading
• use Minimum capitalization
• use italics to distinct from other text
• Number the labels
• assign numbers to allow easy reference
• use either Minimum or MAXIMUM capitalization

11

• Arrange figures
• apart from ordinary text
• top or the bottom of a page, or on a page by
  itself
• place an illustration for a figure
• just before or on the page on which it occurs

12
X
FIGURE 5. Fan data structure.
13
FIGURE 5. Fan data structure, of lists with a
common tail The crossed node is a sentinel.Solid
lines are within-list pointers. Dashed lines are
inter-list pointers.
?
14
Axes, Labels, and Headings

• Space constraints on terms (loose table 11)
• state them in full in the text discussing the
  illustration NATURALLY
• The abbreviations comp., doc., and map.
  stand for compression, document, and mapping
  table respectively.
• The effect of compression on the documents and
  the mapping table is illustrated in the second
  and third rows.
• Unit should be stated in labels
• write Size (bytes), not just Size

15

• Confusing labels by scaling
• an axis labeled as CPU time (seconds
  10-2) ? 50 means 0.5? or 5000?
• discuss typical values to avoid confusing
• Figure 4 shows how time and space trade off as
  node size is varied as can be seen, response of
  under a second is only possible when size exceeds
  11 Kb.