the first orders as 66x66 double-float of a scan with 3 cameras takes 432Mb
when i restart the lisp, the cameras change their order. this is annoying. now i have to figure out how to identify the correct camera after each start
print serial numbers of the cameras
clean up by collecting the region of interest, 1st order coordinates, exposure time and gain in one table
the first element of the *bla* array was always a 0 instead of a list.
store a 64Mb scan file
stored the data from the 3 cameras, initiate a new scan
with step 20 the acquisition takes 6000s
Evaluation took:
  2731.082 seconds of real time
  5921.979000 seconds of total run time (5796.728000 user, 125.251000 system)
  [ Run times consist of 8.982 seconds GC time, and 5912.997 seconds non-GC time. ]
  216.84% CPU
  7,681,963,930,572 processor cycles
  34,209,748,240 bytes consed
as single float scan with step 20 and 3 cameras takes 1.2G
CL-USER> (room)
Dynamic space usage is:   4,469,957,472 bytes.
Read-only space usage is:      5,680 bytes.
Static space usage is:         3,120 bytes.
Control stack usage is:        8,616 bytes.
Binding stack usage is:        1,072 bytes.
Control and binding stack usage is for the current thread only.
Garbage collection is currently enabled.

Breakdown for dynamic space:
  2,914,542,304 bytes for    41,330 simple-array-complex-double-float objects.
  1,241,460,032 bytes for         2 simple-array-complex-single-float objects.
  453,743,424 bytes for 19,053,480 other objects.
  4,609,745,760 bytes for 19,094,812 dynamic objects (space total.)