Changes between Initial Version and Version 1 of 2.2m-UH-8K

Timestamp:

Feb 24, 2009, 4:23:53 PM (17 years ago)

Author:

trac

Comment:

--

2.2m-UH-8K

@@ +1 @@
+Let's run some UH88 Tek cam images in IPP 2.6.1
+(This assumes you've installed IPP 2.6.1 and aren't totally clueless)
+
+== Configuration ==
+
+ * Modifications to site.config
+Add two directories for your data and work files (the Data file isn't crucial)
+
+ UH8KDATA               STR     <where you data is>
+ UH8KWORK               STR     <where IPP can dump its data>
+
+ * Modifications to system.config 
+Add camera information for TEK under "Setups for each camera system" and "camera names as expected by DVO". (This could already be done)
+ CAMERAS                METADATA
+ UH8K           STR     uh8k/camera.config
+
+ DVO.CAMERAS            METADATA
+ UH8K           STR     uh8k
+
+ * Initiating new database
+Create a new project mysql database for your data. (This assumes you've done the preliminary dbadmin setup)
+ dbadmin project DBserver DBuser DBname
+ pxadmin -create -dbname DBname
+Where DBserver, DBuser, and DBname are defined by the user
+
+ * Fits Headers of Input Images
+Here we shall assume a basic knowledge of fits headers and correct setup of the camera. (It is likely your images will be problem free)
+ 
+
+ * Tek's configuration files
+I added a tek config folder under /jfang/psconfig/default.linrh/share/ippconfig/ and named it "tek". In this folder, I copied over isp camera's configuration files from /jfang/psconfig/default.linrh/share/ippconfig/isp/ and edited them:
+
+In format.config, cmf.config, cmp.config:
+Edited the TELESCOP, INSTRUME, and DETECTOR fields. 
+I modified these fields:
+ FPA.NAME       STR     NAXIS
+ CELL.TRIMSEC.SOURCE    STR     VALUE
+ CELL.BIASSEC.SOURCE    STR     HEADER
+ CELL.TRIMSEC           STR     [21:2068,1:2048]
+ CELL.BIASSEC           STR     BIASSEC
+ FPA.FILTER     STR     FILTER
+ CELL.XBIN      STR     CCDBIN1
+ CELL.YBIN      STR     CCDBIN2
+
+In dvo.config:
+ CATDIR                 /media/usbdisk/scr1/catdir.synth.grizy/
+ DATE-KEYWORD           DATE-OBS
+ DATE-MODE              YYYY-MM-DD
+ UT-KEYWORD             UT
+ JD-KEYWORD             JD
+
+In ppImage.config:
+I turned off all dark and shutter fields to FALSE.
+
+In psastro.config, I changed the catalog path:
+ DVO.CATDIR STR /media/usbdisk/scr1/catdir.synth.grizy/
+
+In camera.config, I modified file formats and filter:
+ FORMATS         METADATA
+        TEK     STR     tek/format.config
+        CMP     STR     tek/cmp.config
+        CMF     STR     tek/cmf.config
+ END
+
+ FILTER.ID       METADATA
+ R        STR     R
+ END
+
+ DVO.CAMERADIR  STR     tek
+
+== Data Injection and Registration==
+
+ * How to inject data
+I used the ipp_serial_inject.pl command. Looked at the notes for Essence Test to figure it out. 
+
+ ipp_serial_inject.pl --workdir path://UH8KWORK/ --dbname DBname path_to_data/XXX.fits
+
+The data can be register in one of two ways
+
+ ipp_serial_register.pl --dbname DBname
+
+or by calling pantasks (the data can then be registered in parallel)
+
+ pantasks
+ module pantasks.pro
+ module.tasks
+ all.off
+ controller host add HOSTNAME
+ register.on
+ run
+
+you can observe the status of the processing with 
+ status
+ controller status
+and once the processing is done
+ stop
+
+== Detrend Construction ==
+
+To make the detrend files it is a simple matter of executing the appropriate dettool calls
+
+ dettool -dbname vysostest1 -definebyquery -det_type XXX -filelevel CHIP -workdir path://UH8KWORK/ -inst UH8K -telescope UH88 -select_exp_type YYY
+
+where XXX represents the type of detrend you want to construct (BIAS, FLAT, etc.) and YYY represents the name in the fits headers that corresponds to the appropriate frames (BIAS, FLATFIELD, FLAT, etc.) It is important to call the dettool commands in the correct order (BIAS before DARK before FLAT, etc.) otherwise IPP will crash. 
+
+The dettool places the detrend frames into a queue which can then be executed by pantasks or by
+
+ ipp_serial_detrend.pl --dbname DBname
+
+Many things can go wrong at this point. Maybe IPP expects overscan but your images don't contain it, maybe your fits header is wrong, maybe your trying to make a FLAT before a DARK. Extensive examination of .log and .trace files may be necessary to debug the problem. 
+
+If you have a problem and wish to abort a detrend run, note the number of the run in IPPMonitor and call
+
+ dettool -updatedetrun -dbname DBname -det_id # -state drop 
+
+This will prevent IPP from trying to execute the rest of an aborted run
+
+== Chip and Camera ==
+
+ * The Chip step
+
+Executing the chip step can occur in pantasks or from the command line with
+
+ ipp_serial_chip.pl --dbname DBname
+
+in either case no preliminary calls are necessary. 
+
+ * WCS headers
+
+For the camera step, WCS headers are crucial for the astrometry. Naturally you will need to know this for the camera at the current time. This should already be in the images.
+
+
+ * The camera step
+
+Like the chip step a call in pantasks or from the command line will do
+
+ ipp_serial_camera.pl --dbname DBname
+
+ * How do rerun chip/camera step
+Queue it up again:
+ > chiptool -queue -exp_type OBJECT
+Or you can replace exp_type with whatever field you would like to use in your queue, like a specific image you want to queue up.
+
+== Warping ==
+
+ * To be added when it works
+
+== Difference ==
+
+ * To be added when it works
+
+== Stacking ==
+
+ * To be added when it works