Changeset 15909

Timestamp:

Dec 24, 2007, 11:00:55 AM (18 years ago)

Author:

eugene

Message:

disabling floating-point fuzzing of data; it is not working and it needs to be optional

File:

• trunk/psLib/src/fits/psFitsImage.c (modified) (6 diffs)

trunk/psLib/src/fits/psFitsImage.c

@@ -7 +7 @@
  *  @author Robert DeSonia, MHPCC
  *
- *  @version $Revision: 1.20 $ $Name: not supported by cvs2svn $
- *  @date $Date: 2007-11-16 01:04:56 $
+ *  @version $Revision: 1.21 $ $Name: not supported by cvs2svn $
+ *  @date $Date: 2007-12-24 21:00:55 $
  *
  *  Copyright 2004-2005 Maui High Performance Computing Center, University of Hawaii
@@ -241 +241 @@
 }
 
+# if (0)
+// XXX this needs to be optional (eg, invalid for a mask)
 // Apply the BSCALE and BZERO for an image with a "fuzz"
 // The idea is that the "fuzz" (adding a random number between 0 and 1) preserves the expectation value of
@@ -331 +333 @@
     return out;
 }
-
-
-
+# endif
+
+# if (0)
+// XXX supporting code needs to make this an optional operation
 // Determine BSCALE and BZERO for an image, and generate a new image with it applied
 // TRUE = BZERO + BSCALE * FITS
@@ -411 +414 @@
     return scaleImageWrite(image, bitpix, *bscale, *bzero, rng);
 }
-
+# endif
 
 #if 0
@@ -530 +533 @@
 
     // Quantise floating-point images
+    // XXX this needs to be more controlled: certainly not valid for output masks!
+    # if (0)
     if (PS_IS_PSELEMTYPE_REAL(image->type.type) && fits->bitpix > 0) {
         if (newScaleZero) {
@@ -553 +558 @@
         return scaleImageWrite((psImage*)image, fits->bitpix, *bscale, *bzero, rng);
     }
+    # endif
 
     // Choose the appropriate output type, given the input type and desired bits per pixel