gnuplot-py-users Mailing List for Gnuplot.py

Simon Clift wrote:

>Hi Nate,
>
>>From Nate Gelbard <gelbardn@tr...> 2003-11-06 22:53:
>  
>
>>I have a database query that returns a variable length list of hosts
>>    
>>
>for
>  
>
>>which I want to plot some data about.
>>How can I pass Gnuplot.plot a list of Gnuplot.Data types?
>>    
>>
>I had this problem today and my solution was to use eval():
>  
>
[...]

It is rarely necessary to resort to eval().  In this case, just set up 
the gpd array the way you did and then use eval().  Here I have modified 
your code as described:

>        # plot contents of dKGrid[][] against xKGrid[]
>
>        pobj = Gnuplot.Gnuplot()
>
>        # Snipped out formatting stuff...
>
>        gpd = []            # Array of plot objects.
>
>        for i in xrange( 0, len( yKGrid ) ):
>
>            # Make a list of plot objects
>
>            gpd.append( Gnuplot.Data( xKGrid, dKGrid[i] ) )
>
>        apply(pobj.plot, gpd)    # Execute the plot command
>        pobj.reset()
>  
>

With newer version of Python (starting with 2.0?) you can use the new syntax

    pobj.plot(*gpd)

Michael

-- 
Michael Haggerty
mh...@al...

Hi Nate,

>From Nate Gelbard <gelbardn@tr...> 2003-11-06 22:53:
> I have a database query that returns a variable length list of hosts
for
> which I want to plot some data about.
> How can I pass Gnuplot.plot a list of Gnuplot.Data types?

Sorry I can't reply to the exact thread, I just joined the list.

I had this problem today and my solution was to use eval():

        # plot contents of dKGrid[][] against xKGrid[]

        pobj = Gnuplot.Gnuplot()

        # Snipped out formatting stuff...

        gpd = []            # Array of plot objects.
        gpdStr = ""         # String listing them as arguments

        for i in xrange( 0, len( yKGrid ) ):

            # Make a list of plot objects

            gpd.append( Gnuplot.Data( xKGrid, dKGrid[i] ) )

            if i > 0: gpdStr += ", "            # Comma separate them ...
            gpdStr += 'gpd[%d]' % (i)           # as a list of arguments

        eval( 'pobj.plot( ' + gpdStr + ')' )    # Execute the plot command
        pobj.reset()

Bit late, but I hope this helps...

-- Simon

-- 
Simon Clift                  E-mail: ssclift at math dot uwaterloo dot ca
Ph.D. Student
Scientific Computation Group
University of Waterloo
Waterloo, Ontario, Canada
N2L 3G1

Hello Michael,

Thanks for your response.  I found out what happened and what was going on
with the Terminal window.  I'm pretty sure the "delete" line in the python
demo code caused the original problem (deleting a temp file as you
describe), but the com.Apple.terminal.plist file didn't get updated.  There
is an execution string in this file that needed to get updated with the name
of the last temp file created, and it didn't, so the terminal just logged
out when it couldn't find the file.  Just in case this ever happens to you,
though, see the solution below that my next door neighbor suggested.  It
worked like a charm.

Best Regards,
Rob
-- 
Robert D. Brown III
Partner
Decision Strategies, Inc.
678.947.5997 Phone
928.563.3059 Fax
rb...@de...
http://www.decisionstrategies.com

> Hi Rob,
> 
> Well, for some reason your terminal is executing these two commands (separated
> by semicolon) when you open a window:
> 
> 1) /tmp/501/Cleanup At Startup/1386939.command
> First it tries to run this file. (501 is the user id of the first user created
> on your machine - the OS X admin user.) Dunno what it is, but it can't find it
> and bombs out, but that's ok.
> 
> 2) exit
> This command is the problem - it logs you out of the terminal but doesn't
> close the terminal window, which is why you can't interact with it once it's
> executed.
> 
> The terminal window has a property called "ExecutionString" which apparently
> has been set to these commands. Since you've loaded the dev tools, you should
> have the PropertyListEditor installed in your /Developer/Applications
> directory.
> 
> Now somewhere in /Library/Preferences there should be a file for the default
> terminal window, and it is probably in this file that the ExecutionString is
> set, *unless* you're using custom term files, which would be in
> ~/Library/Application Support/Terminal...called something like foo.term.
> 
> In either case, open up the prefs or term file in PropertyListEditor, find the
> ExecutionString property, and check if it contains these two commands you're
> seeing. If so, clear it out (just select the contents and delete the string)
> and save the prefs / term file.
> 
> I'm not in front of a Mac right now, but I think the directories I'm telling
> you are right...the worst case is we can create a custom term file and have
> that launch when you start terminal. If you haven't used 'em, term files are
> actually quite handy and cool in a geeky way.
> 
> I tried calling but your father-in-law sez you're out for the night. If you're
> around this weekend and still having trouble let me know and I'd be happy to
> look at it. 
> 
> - Vince


> From: Michael Haggerty <mh...@ka...>
> Reply-To: <gnu...@li...>
> Date: Sat, 03 Jul 2004 23:25:23 +0200
> To: <gnu...@li...>
> Subject: Re: [Gnuplot-py-users] Terminal window problems
> 
> Robert Brown wrote:
> 
>> [...]
>> Now when I launch my terminal window without invoking Gnuplot, I get the
>> following message in my terminal window:
>>  
>> 
>>> Last login: Fri Jul  2 14:08:28 on ttyp1
>>> Welcome to Darwin!
>>> Robert-Browns-Computer:~ robertbr$ /tmp/501/Cleanup\ At\
>>> Startup/1386939.command; exit
>>> [Process completed]-bash: /tmp/501/Cleanup At Startup/1386939.command: No
>>> such
>>> file or directory
>>> logout
>>>    
>>> 
> [...]
> 
>> Does anyone see this problem as related to my uncommenting line 108 in the
>> demo.py file?  I am using Mac OS 10.3.4 if this helps.
>>  
>> 
> 
> The "Cleanup At Startup" directory seems to be a Mac place to write
> files that can be deleted without moving them to the trash first.  It
> appears that somebody is writing a command script in that directory
> which should be executed when you log in (e.g., it is run from your
> .profile or .bashrc or whatever Macs use).  But the file is missing for
> some reason.
> 
> Gnuplot.py is certainly not doing anything so elaborate itself.  It
> creates temporary files using filenames generated by Python's standard
> tempfile.mktemp() function then deletes them when the _TempFileItem
> object is destroyed using os.unlink(), and it might be that Python puts
> those files in the "Cleanup At Startup" directory.  But it doesn't write
> any command scripts, and certainly none that are installed into one of
> your startup scripts.
> 
> It's hardly imaginable that the Mac version of Python or gnuplot go to
> such heroic efforts to try to ensure the deletion of temporary files,
> and I don't see any such code in the Python source, so I guess that your
> problem must have arisen from a cause unrelated to Gnuplot.py.
> 
> You might try using grep to find out which script is trying to execute
> that missing file.  Perhaps that will give you further clues.
> 
> Michael
> 
> -- 
> Michael Haggerty
> mh...@al...
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Gnuplot-py-users mailing list
> Gnu...@li...
> https://lists.sourceforge.net/lists/listinfo/gnuplot-py-users

Robert Brown wrote:

>[...]
>Now when I launch my terminal window without invoking Gnuplot, I get the
>following message in my terminal window:
>  
>
>>Last login: Fri Jul  2 14:08:28 on ttyp1
>>Welcome to Darwin!
>>Robert-Browns-Computer:~ robertbr$ /tmp/501/Cleanup\ At\
>>Startup/1386939.command; exit
>>[Process completed]-bash: /tmp/501/Cleanup At Startup/1386939.command: No such
>>file or directory
>>logout
>>    
>>
[...]

>Does anyone see this problem as related to my uncommenting line 108 in the
>demo.py file?  I am using Mac OS 10.3.4 if this helps.
>  
>

The "Cleanup At Startup" directory seems to be a Mac place to write 
files that can be deleted without moving them to the trash first.  It 
appears that somebody is writing a command script in that directory 
which should be executed when you log in (e.g., it is run from your 
.profile or .bashrc or whatever Macs use).  But the file is missing for 
some reason.

Gnuplot.py is certainly not doing anything so elaborate itself.  It 
creates temporary files using filenames generated by Python's standard 
tempfile.mktemp() function then deletes them when the _TempFileItem 
object is destroyed using os.unlink(), and it might be that Python puts 
those files in the "Cleanup At Startup" directory.  But it doesn't write 
any command scripts, and certainly none that are installed into one of 
your startup scripts.

It's hardly imaginable that the Mac version of Python or gnuplot go to 
such heroic efforts to try to ensure the deletion of temporary files, 
and I don't see any such code in the Python source, so I guess that your 
problem must have arisen from a cause unrelated to Gnuplot.py.

You might try using grep to find out which script is trying to execute 
that missing file.  Perhaps that will give you further clues.

Michael

-- 
Michael Haggerty
mh...@al...

I just recently downloaded Gnuplot-Py and have been running it successfully
for several days, namely the demo.py file as I learn how to use Gnuplot-Py.
However, I did have the problem of temporary files being left behind, so I
uncommented line 108 ("# del g, d")

Now when I launch my terminal window without invoking Gnuplot, I get the
following message in my terminal window:
> Last login: Fri Jul  2 14:08:28 on ttyp1
> Welcome to Darwin!
> Robert-Browns-Computer:~ robertbr$ /tmp/501/Cleanup\ At\
> Startup/1386939.command; exit
> [Process completed]-bash: /tmp/501/Cleanup At Startup/1386939.command: No such
> file or directory
> logout

At which point I no longer get a prompt to the Terminal window.

My suspicion is that the Python script deleted the temp file 1386939, but
there is some registry that still maintains that temp file 1386939 still
needs to be deleted.  But I cannot directly confirm that this is related to
the Gnuplot activity.

Does anyone see this problem as related to my uncommenting line 108 in the
demo.py file?  I am using Mac OS 10.3.4 if this helps.

Best Regards,
Rob