This is the first dump of the fisheye code. Please note that it's not really completely mature and will change, so do not use this unless you are prepared and willing to dump the old version completely in favor of new version!
newer version added May 3 by Stubbs
Or not... it appears that I cannot upload a file bigger than about 500kB so I cannot upload the 3.8MB compressed Hipparcos catalog. Sorry, I tried.
...
Blog for using this tarball:
CS images are: * 56717.2500116 * 56717.5972338 * ut030114.0170 * ut030114.0650 Let's if the procedure above works on one of Chris' images, and if so let's bundle it into a script. The input to the script will either be HA, Dec, Az, scale or else a bootstrap file of x,y,RA,Dec. I presume these images were taken at LCO: -70.6926, -29.0146, 2380. Nope, actually from Cerro Pachon, -70.7336, -30.2379, 2647 (-70 44 01.11, -30 14 16.41).
Stomp around ut030114.0170 with monsta and ID some stars:
{{{
1541.3 418.6 95.98789 -52.69565 Canopus
1565.5 1200.2 101.28700 -16.71574 Sirius
583.2 7.2 187.79141 -57.11319 Gacrux
712.3 1346.8 141.89687 -8.65859 Alphard
2064.5 1289.9 78.63445 -8.20166 Rigel
1305.7 1684.8 114.82523 5.22496 Procyon
}}}
Stomp around ut030114.0170 with monsta and ID some stars:
{{{
cat > ut030114.0170.id <<EOF
1541.3 418.6 95.98789 -52.69565 Canopus
1565.5 1200.2 101.28700 -16.71574 Sirius
583.2 7.2 187.79141 -57.11319 Gacrux
712.3 1346.8 141.89687 -8.65859 Alphard
2064.5 1289.9 78.63445 -8.20166 Rigel
1305.7 1684.8 114.82523 5.22496 Procyon
EOF
}}}
and ut030114.0650 (this is way overkill, but I'm adding some named stars):
{{{
cat > ut030114.0650.id <<EOF
961.6 207.2 219.89970 -60.83527 Alp-Cen
1296.0 346.4 187.79141 -57.11319 Gacrux
235.3 730.3 247.35187 -26.43194 Antares
1278.1 1073.0 188.59683 -23.39672 Beta-Crv
1014.0 1329.4 201.29829 -11.16124 Spica
2125.6 1718.2 152.09291 11.96719 Regulus
1571.9 1860.9 177.26526 14.57216 Denebola
2271.1 1211.1 141.89687 -8.65859 Alphard
587.4 1149.9 222.71973 -16.04175 Zubenalgenubi
2650.7 394.1 104.65646 -28.97213 Adhara
EOF
}}}
Let's try it out! Although I don't particularly like nested scripts,
let's bundle fishiter.sh into yet another script, called fishy.sh.
{{{
fishy.sh ut030114.0170.fits LNG=-70.7336 LAT=-30.2379 BOOT=ut030114.0170.id
fishy.sh ut030114.0170.fits LNG=-70.7336 LAT=-30.2379 HA=0 DEC=-28 AZ=94 SCALE=0.046
fishy.sh ut030114.0650.fits LNG=-70.7336 LAT=-30.2379 BOOT=ut030114.0650.id
fishy.sh ut030114.0650.fits LNG=-70.7336 LAT=-30.2379 HA=0 DEC=-28 AZ=94 SCALE=0.046
}}}
This seems to work OK.
Can I get the other two toimages workfrom usingMLO theto known pointingwork?
{{{
cat > 56717.2500116.id <<EOF
971.6 1076.7 101.28700 -16.71574 Rigel
1097.9 762.7 78.63445 -8.20166 Sirius
2377.4 990.7 37.94921 89.26404 Polaris
2187.8 1426.1 165.93221 61.75104 Dubhe
1277.5 1271.4 114.82523 5.22496 Procyon
1456.5 657.3 68.98017 16.50920 Aldebaran
EOF
fishy.sh 56717.2500116.fits LNG=-155.5763 LAT=19.5362 BOOT=56717.2500116.id
fishy.sh 56717.2500116.fits LNG=-155.5763 LAT=19.5362 HA=0.2 DEC=17 AZ=179 SCALE=0.071
fishy.sh 56717.5972338.fits LNG=-155.5763 LAT=19.5362 HA=0.2 DEC=17 AZ=179 SCALE=0.071
}}}
Yes, it works, but it's crucial to get the scale accurate to at least 1%.Explanation of fisheye outputs
RA is right ascension (in J2000)
DEC is declination (J2000 system, we need to talk about that aspect)
HA is hour angle
xcalc is computed expectation of x coord for that cataloged object
ycalc is computed expectation of y coord for that cataloged object
BT is Hipparcos catalog photometry in their BT band
VT is Hipparcos catalog photometry in their VT band
V is computed expectation of V band magnitude
(B-V) is computed expectation of V-R color, in conventional bands
(V-I) is computed expectation of V-I color, in conventional bands
m is Tonry's computed expectation of Canon camera monochromatic magnitude, includes a color term
x is x coord of object centroid in image
y is y coord of object centroid in image
HAcalc is computed expected HA using actual x,y
Deccalc is computed expected DEC using actual x,y
alt is altitude above the horizon, presumably computed from actual x,y
rad is radius, in pixels, from center of the image
minst is instrumental magnitude, i.e. -2.5*log_10(integrated ADU within the aperture used by tphot, after sky subtraction and vignetting correction)
dm is flux uncertainty, expressed in magnitudes
sky is computed background level around the source in question
dvig is the vignetting correction that was applied in obtaining minst, in magnitudes, so we can back out the actual flux value if desired.