Changeset 15388 for trunk/ppstamp/src/ppstampRegion.c
- Timestamp:
- Oct 25, 2007, 5:09:31 PM (19 years ago)
- File:
-
- 1 edited
-
trunk/ppstamp/src/ppstampRegion.c (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/ppstamp/src/ppstampRegion.c
r15363 r15388 3 3 #include "pmHDU.h" 4 4 #include "pmFPA.h" 5 6 #include "ppstamp.h" 5 7 6 8 // Functions to calculate the image space boundaries of a given Chip or Cell … … 20 22 // This is the difference between this function and pmReadoutExtent. 21 23 // pmReadoutExtent ignores the col0, row0 of the readout 22 23 int col0 = 0;24 int row0 = 0;25 24 26 #ifdef notdef 27 if (image->parent) { 28 // This is wrong. I'm trying to deal with the strange megacam 'spliced' images 29 // which appear to have inconsistant CELL.X0 and readout.col0 30 col0 = image->col0 - image->parent->col0; 31 row0 = image->row0 - image->parent->row0; 32 } 33 #endif 34 25 int col0 = 0; // should be image->col0 - readout->col0 26 int row0 = 0; // image->row0 - readout->row0 27 35 28 return psRegionAlloc(col0, col0 + image->numCols, 36 29 row0, row0 + image->numRows); … … 99 92 PS_ASSERT_PTR_NON_NULL(chip, NULL); 100 93 94 if (ppstampMegacamWorkaround) { 95 // There is an inconsistency in the megacam parameters. 96 // The offset to the cells is effectively contained in two 97 // places. 98 // The CELL.X0 for the 2 cells are 0 and 1024 while 99 // readout->image.col0 = 32 and 1056 100 // This fact makes it impossible to calculate the Chip bounds 101 // in a way consistent with say gpc1 102 // we're deferring that problem for now. 103 // Since all chips on megacam have the same bounds, just hard code 104 // the answer. See bug 986 105 return psRegionAlloc(32, 2080, 0, 4612); 106 } 107 101 108 psArray *cells = chip->cells; // Array of component cells 102 109 psRegion *chipExtent = psRegionAlloc(INFINITY, 0, INFINITY, 0); // Extent of chip
Note:
See TracChangeset
for help on using the changeset viewer.
