Changes between Version 65 and Version 66 of HetProcedures/HighSpeedBib

Timestamp:

Oct 30, 2019 5:34:47 PM (5 years ago)

Author:

sco

Comment:

--

HetProcedures/HighSpeedBib

@@ -133 +133 @@
    [[Image(image001.jpg, 600px)]]
 
-You should check that the peak level in the star image is not above appoximately 200 adu (255 is the max, but the peak can vary from frame to frame). A tool that can be use for this is bibtool, which is set up to run on the (default) bmp format images from the vimbviewr gui. Here is an example of how we might view the image named 20191029_0910_9.bmp:
+You should check that the peak level in the star image is not above appoximately 200 adu (255 is the max, but the peak can vary from frame to frame). A tool that can be use for this is bibtool, which is set up to run on the (default) bmp format images from the vimbaviewr gui. Here is an example of how we might view and measure  the image named 20191029_0910_9.bmp:
 
 {{{
   [astronomer@mcs Bib]$  biblook 20191029_0910_9 bmp N
 }}}
-The user places a circle marker around the star and enters a return . At that point the user is shown a 1-line table of values. The header indicates that the second number from the end of the line is the peak value. Here is an example:
+Note that the image basename (20191029_0910_9) and file format (bmp) are specified as two distinct command line arguments. This was done in case the user wished to record other image formats (like tiff). The user places a circle marker around the star and enters a return . At that point the user is shown a 1-line table of values. The header indicates that the second number from the end of the line is the peak value. Here is an example:
 {{{
 # Contents of:  midodata.2