| 229 | | |
| | 229 | == ipptopsps Filters == |
| | 230 | |
| | 231 | The following are the different filters in ipptopsps which may affect the number of items being pushed into psps |
| | 232 | |
| | 233 | detections: |
| | 234 | - force uniqeness on objid |
| | 235 | - deletes anything with PSF_INST_MAG <- 17.5 |
| | 236 | - deletes anything with instFlux < 0.0000001 |
| | 237 | - deletes anything with null instFlux |
| | 238 | - deletes anything with null peakadu |
| | 239 | - deletes anything with null objid |
| | 240 | |
| | 241 | stacks: |
| | 242 | |
| | 243 | - deletes anything with objid = 0 |
| | 244 | - deletes null instFlux |
| | 245 | - deletes null objId |
| | 246 | - deletes null stackApFlx |
| | 247 | - deletes null stackModelFit |
| | 248 | - force uniqness on objid |
| | 249 | - deletes detections not in stackdetection (i'm guessing this is if stuff's been deleted out of stack detection, make sure it also gets deleted out of the oother stack related tables) |
| | 250 | |
| | 251 | objects: |
| | 252 | |
| | 253 | - delete out of range objects (ie, ra/dec out of skytable boundaries) |
| | 254 | - force uniqueness on objId |
| | 255 | |
| | 256 | first looks at the ipptopsps log files suggest that some percent are |
| | 257 | being dropped, mostly by instflux/peakadu in detections... |