[Casa-framework] python object

[jaeger at cpsc.ucalgary.ca]

I didn't get it either, I was wondering if I deleted something accidently
but if I'm not the only one perhaps it just didn't go to anyone.

The attachment was with the reply either.

shannon

ps. we are suppose to get our first snow tomorrow :(


> I didn't receive the first item in this stream of messages.  In
> particular, I didn't get your list of frustrations.
>
> Raymond
>
> On Wed, 13 Sep 2006, Joseph P. McMullin wrote:
>
>> The script sounds a reasonable route (not unlike the old Wim script
>> for sensing this (upfind I think).
>>
>> You also pointed out that the tool.method docstrings are very short
>> and should exploit the content in the xml files - this should be added
>> to the list of things to do later; otherwise, we're back in the
>> familiar territory of having to change interface information in the
>> code and in the documentation separately - not good.
>>
>> Joe
>>
>>
>> On 9/13/06, Kumar Golap <kgolap at nrao.edu> wrote:
>> > My Question is how do we make such scripts automatically be aware of
>> > interface changes in the tools...or at least the programmer should be
>> > warned of dependent scripts.
>> >
>> > When and if i make a change in imager.xml and regenerate a new
>> > interface for the method setimage say...i need to be warned that such
>> > and such tasks are using imager.setimage...so that i can modify them
>> > by hand.
>> >
>> > A simple solution  could just be a small shell script that grep all
>> > the tasks and warn me.
>> >
>> > Kumar
>> >
>> >
>> >
>> > On 9/13/06, Joseph P. McMullin <jmcmulli at nrao.edu> wrote:
>> > > All,
>> > >
>> > > Attached is our first task as Python object. I'm actually reasonably
>> > > happy about this course for being able to quickly implement/modify
>> > > tasks for the users. I did run into some namespace/scope issues
>> > > however that I'd appreciate some feedback on. In particular, I don't
>> > > have access to the global variables within my class/function and so
>> I
>> > > have to recreate my environment. Note, I initially did this as a
>> class
>> > > but then for this single instance changed it to just a function.
>> > > All I need to do is add the error checking and then it will be short
>> > > work to extend this for the other tools. The one issue is whether
>> > > these will be able to interact with the parameter setting interface
>> of
>> > > Darrell - I believe we'll need this.
>> > > Anyway, please review and comment as appropriate. I've also attached
>> a
>> > > list of frustrations that I encountered along the way with the
>> > > stability of things.
>> > > Joe
>> > >
>> > >
>> > > --
>> > > Dr. Joseph P. McMullin         W: +15058357327
>> > > Scientist                               F: +15058357027
>> > > NRAO                             email: jmcmulli at nrao.edu
>> > > 1003 Lopezville Rd
>> > > Socorro, NM 87801
>> > >
>> > >
>> > >
>> > _______________________________________________
>> > Casa-framework mailing list
>> > Casa-framework at donar.cv.nrao.edu
>> > http://listmgr.cv.nrao.edu/mailman/listinfo/casa-framework
>> >
>>
>>
>>
>
> --
> Dr. Raymond Rusk                                        Dr. Raymond Rusk
> ALMA Software Engineer                           Ingénieur Logiciel ALMA
> National Research Council Canada   Conseil national de recherches Canada
> Herzberg Institute of Astrophysics   L'Institut Herzberg d'Astrophysique
> DRAO, P.O. Box 248                                    OFRA, B.P. Box 248
> Penticton, BC V2A 6J9           |\^/|         Penticton, (C.-B.) V2A 6J9
> Government of Canada         _|\|   |/|_          Gouvernement du Canada
> Tel: (250)490-4347           >         <              Tél: (250)490-4347
> Fax: (250)493-7767            >_./|\._<               Fax: (250)493-7767
> Raymond.Rusk at nrc-cnrc.gc.ca
> Raymond.Rusk at nrc-cnrc.gc.ca_______________________________________________
> Casa-framework mailing list
> Casa-framework at donar.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/casa-framework
>