(return to Data Analysis Examples)

Setting up the software and basic configuration

• Last Updated: 2009.08.20

• I've moved the old versions of ipp installations to src/old.install and old code to src/old.src

• I've created an svn branch for changes related to VYSOS, which I've checked out under src/ipp.20090820
• http://svn.pan-starrs.ifa.hawaii.edu/repo/ipp/branches/eam_branches/20090820 ipp.20090820

• I've updated ~/.cshrc to set the PSCONFDIR (installation location) to ~/install

• For the build, I'm using psconfig version ipp.20090805.

• I built the IPP software from the branch above (r25139, was r25003 for 20090805 build)
  • note for r25003 build: hit and fixed an issue with libreadline linkage vs libncurses (see ticket #1284)

• created an ippadmin database and ippadmin user (dropped existing empty ippadmin):
  • ippadmin init localhost ippuser ipp

• created an empty-password ssh key for use by the ipp user:
  • ssh-keygen

• set up the user config files:
  • cp src/ipp.20090805/ippconfig/ipprc.config .ipprc
  • cp src/ipp.20090805/ippconfig/site.config.in install/ipp.20090805.lin64/share/ippconfig/site.config
  • edit site.config to include db host, etc information

• install ippMonitor:
  • cd src/ipp.20090805/ippMonitor/
  • psconfigure --dbhost vysosdata1 --dbuser ippuser --dbpass (XXX) --htdocs /srv/www/htdocs
  • make (failed at first try because of permissions on /srv/www/htdocs)
  • ippMonitor was missing DB.php on the apache server -- see IppMonitor for the fix

Demonstration Data Analysis

• set up a demo database:
  • ippadmin project vysosdata1 ippuser demo_20090806
  • pxadmin -dbname demo_20090806 -create

• inject data (science, flat, dark)
  • ipp_serial_inject.pl --telescope vysos --camera vysos --workdir /home/ipp/data/demo.20090806 --end_stage reg --dbname demo_20090806 newdata/20090630/*.fts
  • ipp_serial_inject.pl --telescope vysos --camera vysos --workdir /home/ipp/data/demo.20090806 --end_stage reg --dbname demo_20090806 newdata/20090630/flats/*.fts
  • ipp_serial_inject.pl --telescope vysos --camera vysos --workdir /home/ipp/data/demo.20090806 --end_stage reg --dbname demo_20090806 newdata/20090630/Calibration/*.fts

• test that pantasks + ssh work:
  • ssh vysosdata1 pclient
  • you should see something like the following:

    pclient: no file /home/ipp/.pcontrolrc
    
    Welcome to PCLIENT - pcontrol client shell
    

• run the registration analysis on the new data:
  • start pantasks; in pantasks, issue these commands:
    • module pantasks.pro
    • module register.pro
    • add.database demo_20090806
    • control host add vysosdata1
    • run
  • register should run for a while; in ippMonitor, entries in 'newExp' should slowly move to 'rawExp'

• Generate Detrend Images
  • For now, the VYSOS5 config applies only bias and flat
  • start & setup pantasks:
    • module pantasks.pro
    • detrend.modules
    • add.database demo_20090806
    • control host add vysosdata1
    • run
  • make a bias:
    • dettool -simple -pretend -dbname demo_20090806 -definebyquery -workdir /home/ipp/data/demo.20090806/detrend -inst VYSOS5 -det_type BIAS -select_exp_type BIAS
      • NOTE with -pretend, the command lists the images to be selected for the bias creation. Remove the -pretend when you are happy with the selection of images to be processed. Without the -pretend option, the command updates the database with the request and reports information about the new detrend image to be created. There will now be an entry in the ippMonitor 'Detrend Steps -> Detrend Runs' page for the master detrend.
    • as the data processes, pantasks status will show the analysis steps being taken.
    • look at the results in ippMonitor Detrend steps
  • make a flat:
    • dettool -simple -pretend -dbname demo_20090806 -definebyquery -workdir /home/ipp/data/demo.20090806/detrend -inst VYSOS5 -det_type FLAT -filter PSr -select_exp_type FLAT -select_filter PSr
  • insert the astrometry model into the detrend database:
    • run script register.astrom.sh in ~ipp/data:
      • ./register.astrom.sh 3 demo_20090806

• Science Processing Example
  • chiptool -simple -pretend -dbname demo_20090806 -definebyquery -dateobs_begin 2009/07/01 -dateobs_end 2009/07/02 -filter PSr -set_label demo.science -set_workdir /home/ipp/data/demo.20090806/demo.science
  • 20090820 : updated registration to convert esoteric OBSTYPE values (eg, light) to controlled values (eg object). set your esoteric OBSTYPE values in camera.config:OBSTYPE.TABLE
  • start & setup pantasks:

    module pantasks.pro
    module chip.pro
    module camera.pro
    control host add vysosdata1
    add.database demo_20090806
    add.label demo.science
    run
    

• Science Processing Example (20090920)
  • chiptool -simple -pretend -dbname demo_20090806 -definebyquery -dateobs_begin 2009/07/01 -dateobs_end 2009/07/02 -filter PSr -set_label demo.20090920 -set_workdir /home/ipp/data/demo.20090920
  • start & setup pantasks:

    module pantasks.pro
    module chip.pro
    module camera.pro
    control host add vysosdata1
    add.database demo_20090806
    add.label demo.20090920
    run
    

Side note on astrometry

• we were having trouble with astrometry in May. I've been looking into this a bit more, and it looks like at least part of the problem is that the angle moves around a bit, and the solution is sensitive to angles of 1-2 degrees. The file ippconfig/vysos5/psastro.config includes an option for searching over a range of angles (PSASTRO.GRID.MIN.ANGLE, PSASTRO.GRID.MAX.ANGLE, PSASTRO.GRID.DEL.ANGLE). I've set this to -20 to +20 in steps of 1 degree. This may not be enough range in some cases.

• it turned out that the FLIPPED images are also flipped relative to the astrometry model. I addressed this by setting FPA.POSANGLE to 180 for the flipped configuration.