Changes between Version 4 and Version 5 of VYSOS5.20091011
- Timestamp:
- Oct 22, 2009, 10:33:21 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
VYSOS5.20091011
v4 v5 22 22 I ran the registration process on the images injected into the database. There are currently 20796 science images and 7819 detrend images. 23 23 24 === Detrend Creation === 24 25 I am generating a master BIAS frame. An unfortunate aspect of the VYSSO5 headers means that the DARK and BIAS images have invalid times (1970/01/01). This makes it difficult to control which input images are used to make a master. I have used a random sample for this initial pass, in the assumption that the camera is reasonably stable. 25 26 … … 34 35 }}} 35 36 36 Ran into trouble with the master flat construction -- it seems ppMerge is leaking some memory and crashing. For now, I've registered the flat from the demo.20090806 database .37 Ran into trouble with the master flat construction -- it seems ppMerge is leaking some memory and crashing. For now, I've registered the flat from the demo.20090806 database (see ~ipp/workdir/register.flat.sh). 37 38 38 Registered the astrometry model. 39 I also registered the astrometry model (see ~ipp/workdir/register.astrom.sh). 40 41 === Sample Science Analysis : IC348 === 39 42 40 43 Launched an analysis of ic348 data: … … 70 73 Initially, I was going to have the processing read from /home/ipp/alldata/... and write results to /home/ipp/data/process. However, it turns out that the directory 'alldata' is a simlink to /drobopro, which is in turn an HFS+ device. Without a lot of work, I cannot NFS mount an HFS+ device on the fruitbowl machines. I decided it would be easier to just copy the data that was going to be processed to /home/ipp/data/rawdata/... and update the database. I defined path://RAWCOPY to point at the new location, and wrote a script (vysosdata1:~ipp/workdir/relocate.ic348) to copy the data and modify the database. Although the script has the ic348 in the name, it will work for any data associated with a labeled chipRun. 71 74 75 2009.10.22: I needed to update the vysos5 database to bring it up to date with recent code changes. But, there seems to have been a recent change to the fruitbowl libraries which broke my IPP build. The IC348 data is processed to chip, but I cannot start camera until this gets fixed. 72 76
