Changes between Version 1 and Version 2 of DVO_GPC1_pt_2

Timestamp:

Apr 29, 2009, 2:42:37 AM (17 years ago)

Author:

Sebastian Jester

Comment:

reformat for trac

DVO_GPC1_pt_2

@@ -5 +5 @@
 
 === Methods ===
+{{{
  [wwoodvas@serenity gpc1] addstar -accept-astrom -D CATDIR test o4732g0168o.34857/o4732g0168o.34857.ch.2676.XY55.cmf
  no data in db test/Photcodes.dat
  directory test does not exist, creating...
  SUCCESS: elapsed time    1.5099 sec for   459 stars (    0 matches),    459 average,     459 measure
-
+}}}
 And you can load all of them with a foreach loop
-
+{{{
  [wwoodvas@serenity gpc1] ls gpc1
  o4732g0168o.34857/
@@ -35 +36 @@
  SUCCESS: elapsed time    0.6230 sec for   160 stars (   22 matches),  16016 average,   16452 measure
  SUCCESS: elapsed time    0.6211 sec for    69 stars (    2 matches),  16083 average,   16521 measure
-
+}}}
 Then we can look at things in DVO:
-
+{{{
  [wwoodvas@serenity gpc1] dvo -D CATDIR gpc1
  no file /Users/wwoodvas/.dvorc
@@ -52 +53 @@
  dvo: mextract -region ra, dec, i, i:err
  dvo: czplot ra dec i 17 12 -c red -pt 7
-
+}}}
 And here's where we see the first problem.  'i:err' is NaN for every value:
-
+{{{
  dvo: limits i i:err
  dvo: limits
  limits: 6.623180 29.526000 nan nan [-a] [-n device]
-
+}}}
 Here we've asked the "limits" function to automatically figure out and set the limits for "i" and "i:err" (for example because we were going to plot them).  It finds that the min and max values for "i:err" are NaN, i.e., all of the values of "i:err" are NaN.  This holds true for all of the filters (griy).  A bit of further investigation reveals that all of the ra:err and dec:err values are 0, but I don't think the inputs to these values from the .cmf value are reasonable in the first place since they tend to be in the 1000s or 0 (are the units on X_PSF_SIG thousandths of a pixel or something?).