From gtaylor@cv3.cv.nrao.edu Thu Aug 31 16:12:13 2000 Date: Tue, 29 Aug 2000 16:53:01 -0600 (MDT) From: gtaylor To: gtaylor Cc: Tim Cornwell , dshepher@zia.aoc.NRAO.EDU, julvesta@zia.aoc.NRAO.EDU, smyers@zia.aoc.NRAO.EDU, gmoellen@zia.aoc.NRAO.EDU, John Hibbard , Athol Kemball Subject: aips++ testing log for August 29 Testing AIPS++ Detailed Log Aug 29, 2000, session: note: TTT = trouble BBB = bug QQQ = question I'm still waiting for Athol to produce a PCAL emulator in aips++. Meanwhile, my bug about the imagerwizard was resolved (I accidently selected 2 fields). So I'm trying that out again. First pass through. Low resolution image of 1751+096 looked ok, but the final image was junk. Now to figure out why... Second pass through the wizard. glish and netscape are competing for all my CPU even though neither one appears to be doing anything useful for the past 10 minutes. Killed both and restarted them. Third pass through the wizard. Trying a simple Clark clean this time. 0.05"/pixel and 512 pixels. 29-Aug-2000/11:29:25: Exception: (/aips++/stable/code/trial/implement/MeasurementEquations/ClarkCleanLatModel.cc : 625) Failed AlwaysAssertExit activePixels.nComp() > 0 29-Aug-2000/11:29:26: imager failed to create restored image 1751+096.spw=12.scale=0.33.restored BBB> And the wizard appears to have abandoned me. Submitted Bug AOCso01713. Starting pass number 4 through the wizard... Tyring Hogbom clean this time. Very quick and it works! Got all the way to my point source image. Tried to go back to see how different inputs affect the clark clean problem above and glish hung up on me again: LocalExec::SetStatus: abnormal child termination for /home/sneffels3/aips++/stable/linux_egcs/bin/glishtk George says this is a longstanding chronic problem of unknown origin. I'll try to get it to repeat. [-- No luck today --] Pass number 5 through the wizard. Trying the mf clean this time. It gives the following severe error: 29-Aug-2000/12:16:09: Zero Pixels selected with a Fluxlimit of 0.011296 and a maximum Residual of 0.0142603 but produces a reasonable looking image. The final map, however, looks completely wacky with two negative holes about as strong as the one positive peak. --- end of testing. Frustration meter reads: |********** | low high