Changes between Initial Version and Version 1 of DVO

Timestamp:

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

Author:

trac

Comment:

--

DVO

@@ +1 @@
+(Up to [wiki:Development_Notes Development Notes])
+
+DGM: [wiki:Astrometry_worries astrometry worries]
+
+DVO Components and related programs
+ * [wiki:DVO_Shell DVO Shell] - user interface tool
+ * [wiki:Addstar addstar] - program to insert objects into the database
+ * [wiki:Delstar delstar] - program to remove objects from the database
+ * [wiki:Getstar getstar] - program to select objects in a region
+ * [wiki:Relphot relphot] - relative photometry analysis and related functions
+ * [wiki:Uniphot uniphot] - photometry zero-points and calibration
+ * [wiki:Relastro relastro] - relative astrometry analysis
+ * [wiki:DvoTools dvoTools] - support tools to interface DVO and IPP
+
+-------
+
+some notes
+
+ * if dvo or mana are unable to interact with kapa, this may be because the binary is not available or because your machine is blocking the port used for the connection (or both).  In the former case (ie, 'which kapa' says 'not found'), you can set $KAPA in the dvo or mana shell to the full path of the binary (eg, $KAPA = /usr/local/bin/mysubdir/kapa).  In the latter case, you can set $KAPA to have "unix://" prepended on the name of the kapa program, telling dvo to contact kapa with a named UNIX socket instead of an INET socket (eg, $KAPA = unix://kapa).  You may combine these two directives, making sure to add the path after unix:// (eg, $KAPA = unix:///usr/local/bin/mysubdir/kapa : the unix:// is stripped and the remainder used as the full path to the executable kapa program).  Alternatively, if you would like to interact explicitly via INET sockets with a kapa on a remote machine, start a stand-alone kapa window on that machine and specify the remote machine with kapa://hostname (eg, $KAPA = kapa://foobar.ifa.hawaii.edu, assuming kapa has been started on foobar).  
+
+ * you may change the dvo catdir anytime from within dvo with the command "catdir".