Fall Workshop in Computational Geometry (FWCG) 2008, 1 Nov 2008, extended abstract, talk, (11/2/2008). Longer papers and talks on the same topic:

1. Analysis of mass properties of the union of millions of polygedra
2. Mass properties of the union of millions of identical cubes]
3. related talk
4. earlier but more detailed talk

1. Parallel ODETLAP for terrain compression and reconstruction. paper, talk.
2. Path planning on a compressed terrain. poster, talk.
3. Evaluating hydrology preservation of simplified terrain representations. poster, talk.

• textbook selection criteria
• Talk Presentation Slide Tools
• Usage notes on assorted SW
• my delicious list
• obligatory quotes
• my old non-wiki home page

• Hearing Loss Association of America - Albany Chapter
• poster on talking to the hard of hearing
• RPI Women's Club
• Janet Franklin
• PA Egleson, 19th century Ottawa merchant

DEC PDP 1, 8, 10, 11, Vax 11/780; IBM 1620, 7094, 360, 370, 5100; Prime; Lisp Machine; Motorola 6811, 68000, 68010, 68020; Sequent Balance; CM-2; Intel 8051, 8086, Pentium, Xeon; Sun Sparc; AMD Opteron.

Wordlengths: 8, 12, 16, 32, 36 (containing 5 7-bit chars plus 1 spare bit)

1. Toggle in a bootstrap loader on the front panel.
2. Read in a paper tape with a text editor.
3. Read in a paper tape with your program, written in assembly.
4. Use TECO to edit your program on the teletypewriter.
5. Punch out a paper tape with the new version of your program.
6. Read in a paper tape with the assembler.
7. Read in the paper tape with your program.
8. Punch out your assembled program.
9. Read in your assembled program.
10. Run it.
11. Correct small errors by toggling on the front panel new values for certain words in core.
12. For big errors, go back to step 2.

1. Write out your program on paper.
2. Punch your program onto cards, one card per line, using a machine called a keypunch, the size of a desk.
3. Correct any typos by inserting a card into a read slot in the keypunch, duplicating it onto a new card up to the typo, typing the correct char, and then duplicating the rest of the line.
4. If a card is damaged it may jam in the keypunch. Use a card saw (like a hacksaw blade) to pry it out in pieces.
5. Add job control cards before and after your program to tell the computer how to compile and run it and what files it will read and write. When creating a new file, specify a few parameters:
   1. name
   2. volume it will go in (like a partition)
   3. whether to catalog it (so future users don't need to know the partition)
   4. is the file new or existing?
   5. disposition when the job finishes, e.g., keep or delete
   6. disposition if the job ends abnormally
   7. type of units of storage to allocate, e.g., cylinder or track
   8. number of those units
   9. number more to allocate whenever more space is needed
   10. whether to keep or release any extra storage at the end
   11. format of records in the file, e.g., fixed or variable length
   12. if fixed, the record length
   13. how the records are grouped into blocks
   Most of the above are required and do not have useful defaults. Example:
   //SYSUT2 DD DSN=MYFILE,DISP=(NEW,KEEP,DELETE),
   // SPACE=(CYL,(5,1),RLSE),RECFM=(FB,80,3200)
6. Use a magic marker to draw a diagonal line across the top edge of the card desk to aid in sorting the cards if you drop them.
7. Read the card deck into the computer.
8. Wait for it to print out the result on 15" wide fanfold paper.
9. Examine the output. Add lines to your program by punching new cards and inserting them into the deck.
10. Repeat.