From gtaylor@cv3.cv.nrao.edu Mon Jul 31 15:42:59 2000
Date: Mon, 31 Jul 2000 15:25:23 -0600 (MDT)
From: gtaylor <gtaylor@cv3.cv.nrao.edu>
To: Greg Taylor <gtaylor@zia.aoc.NRAO.EDU>
Cc: dshepher@pegaso.aoc.nrao.edu, julvesta@pegaso.aoc.nrao.edu,
     smyers@pegaso.aoc.nrao.edu, tcornwel@pegaso.aoc.nrao.edu
Subject: aips++ testing log for July 28

  
               Testing AIPS++  Detailed Log

July 28, 2000, session:

note: TTT = trouble
      BBB = bug
      QQQ = question

Started out trying to edit away some stray visibilities.  Editing tools
are very rough, not yet functional.  In conversation with Steve and
Debra we have deferred testing of these tools for the moment.  What we
really need to do is sit down with whoever is going to be programming
these and discuss some philosophy and mechanics of how best to flag
data.  Current direction for the implementation doesn't look good.

Carried out flagging in AIPS, ran UVCOP to drop flagged data, and then
transfered this data to aips++.  Used the scripter tools to run through
the calibration a bit more quickly.  

Getting visplot up and running takes 5 minutes.  Seems rather long.
What is it doing?

BBB> upon inspection I see that my data is not calibrated.  So I 
go back to calibrater and try to apply the CLEDT table I made.

Caught an exception! Event type=run exception=(/aips++/daily/code/trial/implement/MeasurementComponents/DOcalibrater.cc : 460) Failed AlwaysAssertExit retval
assigned AIPS++ defect AOCso01574:

No go and nobody around.  Giving up for the day.  Should have gone fishing.

Resolution (July 31).  Athol points out that the integration time 
in setapply has to be set to 0.  Failure to do so results in the above
obscure error message.  He will remove this field for the moment until
he decides what purpose (if any) it serves.

--- end of testing.  
Frustration meter
reads: |**************    |
        low            high