- Timestamp:
- Dec 14, 2010, 9:01:22 AM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/eam_branches/ipp-20101205/psModules/src/objects/pmTrend2D.c
r30020 r30029 179 179 } 180 180 181 bool pmTrend2DFit( pmTrend2D *trend, psVector *mask, psVectorMaskType maskVal, const psVector *x,181 bool pmTrend2DFit(bool *goodFit, pmTrend2D *trend, psVector *mask, psVectorMaskType maskVal, const psVector *x, 182 182 const psVector *y, const psVector *f, const psVector *df) 183 183 { … … 189 189 190 190 bool status = false; 191 bool goodFit = false; 191 *goodFit = false; 192 // for the psImageMap fit, it is possible to have valid data but no valid solution for 193 // example, an isolated cell may not be reached from other cells, making the solution 194 // degenerate. psImageMapFit should probably handle this case, but until it does, we allow 195 // it to fail on the result, but not yield an error (goodFit = false). 196 // psVectorClipFitPolynomial2D can not fail in this way (really?), so goodFit is always 197 // true 192 198 193 199 switch (trend->mode) { … … 198 204 // of points in the image, and potentially based on the fractional range of the 199 205 // data? 206 *goodFit = true; 200 207 break; 201 208 … … 203 210 // XXX supply fraction from trend elements 204 211 // XXX need to add the API which adjusts the scale 205 status = psImageMapClipFit( &goodFit, trend->map, trend->stats, mask, maskVal, x, y, f, df);212 status = psImageMapClipFit(goodFit, trend->map, trend->stats, mask, maskVal, x, y, f, df); 206 213 break; 207 214
Note:
See TracChangeset
for help on using the changeset viewer.
