Index: /branches/eam_branches/20091201/psastro/src/psastroLoadCrosstalk.c
===================================================================
--- /branches/eam_branches/20091201/psastro/src/psastroLoadCrosstalk.c	(revision 26876)
+++ /branches/eam_branches/20091201/psastro/src/psastroLoadCrosstalk.c	(revision 26877)
@@ -193,4 +193,7 @@
               continue;
             }
+	    // czw: 2010-01-27 
+	    // Potential new crosstalk: OTA4yXY5v <=> OTA4yXY6v
+	    // Currently not enough info to be convinced of this, however, as the artifacts are very faint.
 
             // Calculate destination positions
Index: /branches/eam_branches/20091201/psastro/src/psastroZeroPoint.c
===================================================================
--- /branches/eam_branches/20091201/psastro/src/psastroZeroPoint.c	(revision 26876)
+++ /branches/eam_branches/20091201/psastro/src/psastroZeroPoint.c	(revision 26877)
@@ -43,8 +43,8 @@
     // given the existing per-chip astrometry, determine matches between raw and ref stars
     // is this needed? yes, if we didn't do SingleChip astrometry first
-    if (!psastroMosaicSetMatch (fpa, recipe, 0)) {
-        psError(PSASTRO_ERR_UNKNOWN, false, "failed to match raw and ref stars for mosaic");
-        return false;
-    }
+    // if (!psastroMosaicSetMatch (fpa, recipe, 0)) {
+    //     psError(PSASTRO_ERR_UNKNOWN, false, "failed to match raw and ref stars for mosaic");
+    //     return false;
+    // }
 
     // XXX eventually: look up the photcode info from the recipe, use the ZEROPT and A_0 terms
@@ -147,5 +147,5 @@
 
     // XXX make this depend on the mode?
-    if (dMag->n < 3) {
+    if (!dMag || dMag->n < 3) {
       fprintf (stderr, "zero point NaN +/- NaN\n");
       return false;