IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Initial Version and Version 1 of DVO_FAQ


Ignore:
Timestamp:
Feb 24, 2009, 4:23:54 PM (17 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DVO_FAQ

    v1 v1  
     1Frequently Asked Questions : DVO
     2
     3==== How do I update the list of photcodes ? ====
     4
     5Your .ptolemyrc file specifies the location of a PHOTCODE_FILE as well as a CATDIR, usually with something like:
     6
     7 CONFDIR                 /home/panstarrs/ipp/psconfig/ipp-2.6.lin64/share/ippconfig
     8 PHOTCODE_FILE          $CONFDIR/dvo.photcodes
     9 # location of DVO database tables
     10 CATDIR                 /data/ipp003.0/catdir
     11
     12If you want to update the photometry codes, you will have to edit that dvo.photcodes file or specify the location of a new one. But if you have already created a DVO catdir, then the photcodes are locked in place.  Any dvo programs like addstar or dvo itself will pick up the photcodes from the Photcodes.dat file in your CATDIR, not from the PHOTCODE_FILE.  So after updating your PHOTCODE_FILE, you must delete the Photcodes.dat file from your CATDIR.  Then when you run something like addstar, a new Photcodes.dat file will be automatically created.
     13
     14==== addstar is reporting a "bad astrometric solution in header."  How do I get around that? ====
     15
     16You probably have an astrometric error term that exceeds the allowable range.   The parameter ADDSTAR_MAX_CERROR can be specified in your camera's dvo.config file.  Try increasing this parameter.   To change it at the command line you can use :
     17
     18 addstar -D ADDSTAR_MAX_CERROR 5.0  ...
     19
     20==== After processing a set of overlapping images, there are too many stars in the catalog. What's wrong? ====
     21
     22You may need to re-sort the dvo catalog.  In the normal camera stage processing, each new photometry file is added to the database without any sorting of detected objects (because this is a time-consuming process).  Use the following to sort your overlapping catalogs and coordinate multiple occurrences of the same object:
     23
     24 addstar -resort -D CATDIR mycatdir
     25
     26To specify the radius (in arcseconds) for determining a match, use
     27
     28 addstar -resort -D CATDIR mycatdir -D RADIUS 1.5 
     29
     30or edit the appropriate dvo.config file for your camera.
     31
     32==== I've got a perfectly good .smf file, but I can't see any stars.  What's wrong? ====
     33
     34You might have an error in your .ptolemyrc file.
     35Compare your .ptolemyrc file to the dvo.site file from the ipp installation you are using.
     36
     37
     38==== How do I set up my .ptolemyrc file? ====
     39
     40Here is an example .ptolemyrc that functions with GPC1 data as of ipp-2.6 :
     41
     42<pre>
     43CONFDIR                 /home/panstarrs/ipp/psconfig/ipp-2.6-bills.lin64/share/ippconfig
     44CAMERA                  default
     45
     46# location of DVO database tables
     47CATDIR                  default
     48
     49# location of possible data sources
     502MASS_DIR_AS            NONE
     512MASS_DIR_DR2           NONE
     52GSCDIR                  NONE
     53USNO_A_DIR              NONE
     54USNO_B_DIR              NONE
     55TYCHO_DIR               NONE
     56
     57PHOTCODE_FILE           $CONFDIR/dvo.photcodes
     58GSCFILE                 $CONFDIR/GSCregions.tbl
     59CATMODE                 SPLIT
     60CATFORMAT               PS1_DEV_1
     61SKY_DEPTH               3
     62# SKY_TABLE             this may be used to override GSCFILE
     63ZERO_PT                 25.0
     64
     65# access control for client/server addstar mode
     66# PASSWORD
     67# HOSTNAME
     68# VALID_IP
     69
     70# camera dependent parameter files:
     71FILTER_LIST             $CONFDIR/$CAMERA/dvo.filters
     72CAMERA_CONFIG           $CONFDIR/$CAMERA/dvo.layout
     73DETREND_RECIPES         $CONFDIR/$CAMERA/dvo.recipe
     74
     75# load the camera-specific configuration files
     76input                   $CONFDIR/$CAMERA/dvo.config
     77
     78</pre>
     79
     80
     81==== How can I access info from the mysql database tables within DVO? ====
     82Use <code>dbconnect</code> to connect to the database and <code>dbselect</code> to collect the data.
     83
     84<pre>
     85dvo: dbconnect
     86USAGE: dbconnect (hostname) (username) (database)
     87
     88dvo: dbselect
     89USAGE: dbselect (fields) from (table) [where]
     90</pre>
     91
     92Here is an example using the '''gpc1''' database that extracts some vectors from the MD09 chip processing output.
     93
     94<pre>
     95dvo:  dbconnect  hostmachine  uid gpc1
     96dvo: dbselect chipProcessedImfile.class_id,chipProcessedImfile.fwhm_major,chipProcessedImfile.fwhm_minor,chipProcessedImfile.n_stars,chipProcessedImfile.n_astrom,chipProcessedImfile.sigma_ra,chipProcessedImfile.sigma_dec FROM chipProcessedImfile,chipRun,rawExp  WHERE chipProcessedImfile.chip_id=chipRun.chip_id AND chipRun.exp_id=rawExp.exp_id AND rawExp.ra >= '5.8' AND rawExp.ra <= '5.9' AND rawExp.decl >= '-0.1' AND rawExp.decl <= '0.1' AND rawExp.exp_time>60 AND chipProcessedImfile.fault=0 AND chipRun.state='full'
     97</pre>
     98
     99
     100==== How do I create/manipulate a vector/array of values? ====
     101Create vectors from scratch with the <code>create</code> function   Example:
     102
     103 create x 0 100 0.1
     104
     105creates a vector called x with 100 values spaced in increments of 0.1, starting at 0.
     106
     107Perform arithmetic, etc. with the <code>set</code> function.   Use
     108
     109 help set
     110
     111to see detailed help and examples.
     112
     113==== How do I make a histogram of a vector or an image? ====
     114The internal dvo documentation (available via <code>help</code> or <code>?</code>)  is a bit confusing for this. 
     115
     116<code>histogram</code> computes the histogram of a ''vector'' (a list of numbers).
     117The usage line for this function should be:
     118 USAGE: histogram invec outvec start end [delta]
     119
     120<code>imhist</code> computes the histogram of an ''image''
     121The usage line should read:
     122 USAGE: imhist <buffer> <x> <y> [-region sx sy nx ny] [-range min max] [-delta binsize]
     123
     124'''Ignore the response you get from <code>help histogram</code>'''
     125
     126==== How do I make plots of vectors and how do I set the plotting style? ====
     127Use the <code>plot</code> and <code>style</code> functions.  Check out the dvo help pages with:
     128
     129 help plot
     130 
     131 help style
     132
     133See also <code>lim</code> and <code>box</code>
     134
     135==== How do I save a plot or image to a printable file? ====
     136All of these ''should'' save the current active Kapa window as a file:
     137 png outfile.png
     138 jpeg outfile.jpeg
     139 ps outfile.ps
     140
     141Presently (as of 080814) only the ps command uses the output filename correctly (png saves to ''kapa.png'' regardless of the provided filename) and the <code>jpeg</code> command doesn't seem to do anything at the moment.
     142
     143==== Why does addstar say "Error in config: can't find RADIUS"? ====
     144
     145This error occurs when addstar can't find a dvo.config file referenced via 'input' in your ~/.ptolemyrc like so:
     146
     147 input                   $CONFDIR/$CAMERA/dvo.config
     148
     149<code>CONFDIR</code> is the config directory (typically defined earlier in ~/.ptolemyrc).
     150
     151<code>CAMERA</code> is the camera name, either also from ~/.ptolemyrc or given on the addstar command line with <code>-D CAMERA camname</code>.
     152
     153All of these are case-sensitive (except perhaps on a Mac), so you need to give $CONFDIR and $CAMERA in exactly the capitalization as the corresponding directories on your disk, and the directory and file need to exist, of course. [http://pan-starrs.ifa.hawaii.edu/bugzilla/show_bug.cgi?id=1100 Bug 1100] asks for a clearer error message.