Changes between Version 77 and Version 78 of HetProcedures/HighSpeedBib

Timestamp:

Oct 31, 2019 7:28:04 PM (5 years ago)

Author:

stevenj

Comment:

--

HetProcedures/HighSpeedBib

@@ -134 +134 @@
 
 8b. [=#bibtool] Check the peak signal. 
-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 used 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:
+You should check that the peak level in the star image is not above approximately 200 adu (255 is the max, but the peak can vary from frame to frame). A tool that can be used for this is bibtool, which is set up to run on the (default) bmp format images from the vimbaviewer GUI. Here is an example of how we might view and measure the image named 20191029_0910_9.bmp:
 {{{
   [astronomer@mcs Bib]$  biblook /hetdata/data/ImageQuality/20191029/Bib/20191029_0910_1017.bmp N
@@ -146 +146 @@
 You can answer "N" to the 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 82 adu. This would be a safe level for taking high speed BIB images. 
 
+8c. Another option is {{{{ds9bib}}} which displays a TIFF BIB image in ds9, with a contour showing any pixels above 200 counts. Use:
+{{{
+[astronomer@mcs ~]$ ds9bib /hetdata/data/ImageQuality/20191021/Bib/20191021_1124_1881.tiff
+}}}