| 24 | | * discovered a serious problem with the sky calibration run processing. psastro was not correctly handling stack inputs. Stacks are set to have a zero point of 25 but the code that psastro used to convert from instrumental magnitude to magnitude for the reference catalog lookup used the nominal zero points for single frame exposures. This had the result that the selection of stars retrieved from the catalog did not match the stars selected for the astronomical fit. This caused psastro to decide that the data was bad and assigned it bad quality. This did not affect any skycells in our test data set SAS so we didn't notice this problem. The end result is about 1/3 of our stack data was lost before being imported into DVO and this PSPS. Since the difference between the single exposure zero point and 25 was largest for y band it was most affected. 2/3 of skycells were rejected. |
| 25 | | * Fixed the psastro bug and restarted the skycal processing. Reran Kepler wedge for dec > 20 degrees. For staticsky deferred the galactic center for now and started working on stripes of RA starting in the east at 10 hours. Comparison of the first two plots at http://svn.pan-starrs.ifa.hawaii.edu/trac/ipp/wiki/staticsky.20120706 shows the progress over the weekend. At this rate staticsky should be complete for 9.5 hours < RA < 20 hours by |
| 26 | | the end of the week. |
| 27 | | * Prior to the above spent some time shepherding the data near the galactic plane through. We have a performance problem for very dense regions. |
| | 24 | * discovered a serious problem with the sky calibration run processing. psastro was not correctly handling stack inputs. Stacks are set to have a zero point of 25 but the code that psastro used to convert from instrumental magnitude to magnitude for the reference catalog lookup was using the nominal zero points for single frame exposures. This had the result that the selection of stars retrieved from the catalog did not match the stars selected for the astronomical fit. This caused psastro to decide that the data was bad and assigned it bad quality. This did not affect any skycells in our SAS test data sets so we were not aware of this problem. The end result is about 1/3 of our stack data was lost before being imported into DVO and thus PSPS. Since the difference between the single exposure zero point and 25 was largest for y band it was most affected. 2/3 of skycells were rejected. DVO ingest and thus PSPS ingest will need to be restarted. |
| | 25 | * Fixed the psastro bug and started over with the skycal processing. Reran Kepler wedge for dec > 20 degrees. For staticsky deferred the galactic center for now and started working on stripes of RA starting in the east at 10 hours. Comparison of the first two plots at http://svn.pan-starrs.ifa.hawaii.edu/trac/ipp/wiki/staticsky.20120706 shows the progress over the weekend. At this rate staticsky should complete for the region with 9.5 hours < RA < 20 hours by the end of the week. This will provide many options for how we proceed with loading PSPS. |
| | 26 | * Prior to the above spent some time shepherding the data near the galactic plane through staticsky. We have a performance problem for very dense regions. |
