Changes between Version 54 and Version 55 of Sa10Problems
- Timestamp:
- Dec 13, 2012, 11:24:10 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Sa10Problems
v54 v55 107 107 * C. PSPS flags: 108 108 * C1. objectxflags: what does ID_SECF_HAS_STACK correspond to: forced photometry on the stack if set? Not clear why it should indicate whether there is a stack photometry as if there isn't any, then the corresponding photometry column should be set to -999 109 * a. ? '''Gene???'''109 * a. '''EAM : currently this is supposed to be set if stack photometry exists for the object in the filter, regardless of the quality, but in fact it can be skipped if the input measurements are skipped : this needs to be fixed''' 110 110 * D. PSI/PSPS suggestions: 111 111 * D1. It would be good if a small command could be defined for this expression int_ran = (ippobjid % 10) *1000 + ((objid / 10000) % 10)*100 + ((ippobjid / 10) % 10)*10 +(objid % 10) . The neat part of int_ran is that it runs from 0 to 9999 and is randomly distributed. It can be selected from nearly all tables directly in a repeatable fashion. int_ran is very quick to compute (barely increases the runtime of the query). Equally important (if not key), one can match tables which were selected on the same int_ran condition, making it far superior than any true random number associated with any table. The only flaw is that one cannot select any fraction smaller than 1/10000, i.e. 0.01%, but I believe this will rarely be of interest.
