| 45 | | The code is essentially the same as that used for SAS_32 except that the selection of objects for extended model fitting was relaxed. In particular |
| 46 | | the previous requirement that the object be "extended" (EXTNSIGMA > 3) is not used. Instead magnitude cuts were used.The cuts chosed are 21.5 in g, r, and i. 20.5 in z and 19.5 in y band. Note that these cuts are per object. If the object's magnitude was less |
| 47 | | than the cut for any band, fits were performed in all bands. |
| | 45 | The code is essentially the same as that used for SAS_32 except that the selection of objects for extended model fitting in psphotStack was relaxed. In particular |
| | 46 | the previous requirement that the object be "extended" (EXTNSIGMA > 3) is not applied. Instead magnitude cuts were used.The cuts chosed are 21.5 in g, r, and i. 20.5 in z and 19.5 in y band. Note that these cuts are per object. If the object's magnitude was less |
| | 47 | than the cut for any band, fits were performed in all bands. In 3PI.PV2 extended model fits will not be performed in the region within 20 degrees latitude of the galactic plane with the limit increasing to 35 degrees near the galactic center. |
| | 48 | |
| | 49 | During the skycal processing a new data product is produced. The "cff file". Here are contained the measurements for each source that are to be |
| | 50 | used for forced photometry. Each source with an with a extended source fit is marked for galaxy fitting. |
| | 51 | |
| | 52 | The inputs to each "full force run" are the cff file (one per skycell per filter) and the set of individual warps for each skycell. In this data set there were |
| | 53 | on average 11 warps per skycell. |
| | 54 | |
| | 55 | The full force processing consists of two parts. Running psphotFullForce on the individual warps followed by psphotFullForceSummary to generate the |
| | 56 | final extended source measurements for each source. See [wiki:fullforce_algorithms] for details on the measurements and calculations. |
