Changes between Version 64 and Version 65 of HetProcedures/HighSpeedBib

Timestamp:

Oct 30, 2019 5:31:29 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 no above 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 vimbviewr gui. Here is an example of how we might view the image named 20191029_0910_9.bmp:
 
 {{{
-  biblook 20191029_0910_9 bmp N
-
+  [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 indicatess that the second number from the end of the line is the peak value. Here is an example:
+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
@@ -154 +153 @@
    106.04     79.07    106.62     78.27  21.475    91.238    87.188      635.0     204.33   1
 }}}
+You can answerr "N" to the next couple questions about cleaning files. It is the usual case that we delete all of the ASCII files made in this process since we are usually just measuring test images in preparation for taking the real data. In the above example we see that the peak level measured in our star image was 204 adu. This would be a safe level for taking high speed BIB images. 
+