gnuplot-py-users Mailing List for Gnuplot.py

Hello,

Thank you. I'm a beginning Linux user and I didn't install
python-numeric. Everything seems to work all right now.

Best regards,

Tom 

Hi Tom

> ImportError: No module named Numeric

You need to install the numeric extension to python.
http://www.pfdubois.com/numpy/

You can install from source, but also
some linux distributions include it.
For instance, in my Mandrake 9.2 the package is 
python-numeric-22.0-4mdk

Good luck
-- leo

On Tue, 23 Dec 2003, Tom Mortier wrote:

> Hello,

Hello,


I've got a problem with the installation of gnuplot-py. I tried to
install gnuplot-py like in the README file or on the webpage:

1. Download gnuplot-py-1.7.tar.gz
                                                                       
                                                 
2. Extract the archive to a temporary directory. I used tar -xvf
gnuplot-py-1.7.tar.gz
                                                                       
                                                     
3. Install by changing to the directory and typing "python setup.py
   install".

When I gave the command python setup.py install , the computer gave this
output :
Traceback (most recent call last):
  File "setup.py", line 17, in ?
    from __init__ import __version__
  File "__init__.py", line 167, in ?
    from PlotItems import PlotItem, Func, File, Data, GridData
  File "PlotItems.py", line 26, in ?
    import Numeric
ImportError: No module named Numeric

I don't know what the problem is. Has somebody been having the same
problem ?

Best regards,

Tom 

I have searched the documentation and the archive and have not found how to
plot data with error bars.  Could someone please point me in the right
direction.  A short piece of code would be helpful

--------------------------------
James B. Maciokas, Ph.D
University of California, Davis
Center for Neuroscience
1544 Newton Ct
Davis, CA  95616-8768
Tel:  (530) 757-5081
Fax:  (530) 757-5247

jbm...@uc...
--------------------------------

James Maciokas wrote:

>Could someone please point me in the right direction for list of available
>plot types?  I have searched the documentation and the mailing list without
>success.
>
>Some example plots with errorbars would be most helpful.
>

The styles of plotting are documented within gnuplot under the help 
system; type "help plot with" and "help set style" to get info.  To plot 
with errorbars under Gnuplot.py, you need either 3 (x,y,delta) or 4 
(x,y,ylow,ymax) columns of data and then specify the "with='errorbars'" 
option:

 >>> import Gnuplot
 >>> g = Gnuplot.Gnuplot()
 >>> g('set xrange [0:5]')
 >>> g.plot(Gnuplot.Data([[1,2,0.1],[2,3,0.2], [3,4,0.3]], 
with='errorbars'))
 >>> g.plot(Gnuplot.Data([[1,2,1.5,2.2],[2,3,2.8,3.3], [3,4,3.2,4.7]], 
with='errorbars'))

Hope that helps.
Michael

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

Could someone please point me in the right direction for list of available
plot types?  I have searched the documentation and the mailing list without
success.

Some example plots with errorbars would be most helpful.

Thanks for your help...

--------------------------------
James B. Maciokas, Ph.D
University of California, Davis
Center for Neuroscience
1544 Newton Ct
Davis, CA  95616-8768
Tel:  (530) 757-5081
Fax:  (530) 757-5247

jbm...@uc...
--------------------------------

Nadav,

The dependence on the version of Gnuplot.py is strange.  Aside from the 
difference between FIFOs and temporary files, which the option change 
reverses, I don't understand why they behave differently.  Do you need 
to use a different gnuplot terminal type to get the mouse features?  If 
so, there is an option "default_term" in gp_*.py that you might try 
playing with.

I suggest that you create the Gnuplot object with the option 
Gnuplot(debug=1).  This will display each of the commands being sent by 
Gnuplot.py to gnuplot.  If you compare the commands sent by 1.6 and 1.7 
the difference might lead you to an explanation.

I currently don't have gnuplot 3.8 installed on my computers so I can't 
test things myself.  I'll try it out when I get a chance (which might 
not be very soon).

Michael

Nadav Horesh wrote:

> I tried again, but now it seems that the mouse command don t pass 
> through to gnuplot --- no coordinates display, no zoom etc. Switching 
> back and forth between 1.6 and 1.7 reveal that it is 1.7 problem only.
>
>  Nadav.
>
> Nadav Horesh wrote:
>
>> Thank you for your replay, I'll try to make the patch and test it again.
>> The option to mouse-interact with gnuplot's graphics window  was 
>> introduced in gnuplot 3.8. It works under X11, and win32 and probably 
>> under some other OS's.
>> I have tested gnuplot-py 1.7 + gnuplot 3.8 combination only under 
>> gnu/linux. I had no problems with gnuplot-py 1.6 + gnuplot 3.8 under 
>> win32.
>>
>>   Nadav
>>
>>> Under linux I can not use gnuplot's mouse interaction ((un)set grid, 
>>> (un)zoom, etc.). It looks like gnuplot reread the data file on every 
>>> operation, thus it conflicts with the pipe interface introduced in 1.7.
>>>
>>> Any work-around (beside going back to 1.6)? 
>>


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

I tried again, but now it seems that the mouse command don t pass 
through to gnuplot --- no coordinates display, no zoom etc. Switching 
back and forth between 1.6 and 1.7 reveal that it is 1.7 problem only.

  Nadav.

Nadav Horesh wrote:
> Thank you for your replay, I'll try to make the patch and test it again.
> The option to mouse-interact with gnuplot's graphics window  was introduced in gnuplot 3.8. It works under X11, and win32 and probably under some other OS's.
> I have tested gnuplot-py 1.7 + gnuplot 3.8 combination only under gnu/linux. I had no problems with gnuplot-py 1.6 + gnuplot 3.8 under win32.
> 
>   Nadav
> -----Original Message-----
> From:	kai...@t-... [mailto:kai...@t-...]
> Sent:	Sat 13-Dec-03 22:42
> To:	gnu...@li...
> Cc:	
> Subject:	Re: [Gnuplot-py-users] gnuplot-py 1.7 and gnuplot 3.8 mouse-interaction conflict
> Nadav Horesh wrote:
> 
> 
>>Under linux I can not use gnuplot's mouse interaction ((un)set grid, 
>>(un)zoom, etc.). It looks like gnuplot reread the data file on every 
>>operation, thus it conflicts with the pipe interface introduced in 1.7.
>>
>>Any work-around (beside going back to 1.6)? 
> 
> 
> 
> Sorry I didn't respond earlier.  I was on vacation.
> 
> I am not familiar with the commands that you mentioned.  On what gnuplot 
> version and platform are they?  Are they specific to a particular 
> terminal type?
> 
> If this feature causes gnuplot.py to read the input file twice, that 
> would indeed be a problem when working with FIFOs.  Normally, as soon as 
> the FIFO has been read once by gnuplot, it is deleted.  It would be 
> possible to keep the FIFO around for possible repeated reads, but this 
> would defeat the purpose of the FIFO (which was to enable Gnuplot.py to 
> know when it is safe to discard old data).
> 
> As for a workaround, you can go back to using temporary files as a 
> default by going to the gp_*.py file specific to your platform (e.g., 
> gp_unix.py or gp_macosx.py) and changing the option "prefer_fifo_data" to 0.
> 
> Michael
> 

Thank you for your replay, I'll try to make the patch and test it again.
The option to mouse-interact with gnuplot's graphics window  was =
introduced in gnuplot 3.8. It works under X11, and win32 and probably =
under some other OS's.
I have tested gnuplot-py 1.7 + gnuplot 3.8 combination only under =
gnu/linux. I had no problems with gnuplot-py 1.6 + gnuplot 3.8 under =
win32.

  Nadav
-----Original Message-----
From:	kai...@t-... [mailto:kai...@t-...]
Sent:	Sat 13-Dec-03 22:42
To:	gnu...@li...
Cc:=09
Subject:	Re: [Gnuplot-py-users] gnuplot-py 1.7 and gnuplot 3.8 =
mouse-interaction conflict
Nadav Horesh wrote:

> Under linux I can not use gnuplot's mouse interaction ((un)set grid,=20
> (un)zoom, etc.). It looks like gnuplot reread the data file on every=20
> operation, thus it conflicts with the pipe interface introduced in =
1.7.
>
> Any work-around (beside going back to 1.6)?=20


Sorry I didn't respond earlier.  I was on vacation.

I am not familiar with the commands that you mentioned.  On what gnuplot =

version and platform are they?  Are they specific to a particular=20
terminal type?

If this feature causes gnuplot.py to read the input file twice, that=20
would indeed be a problem when working with FIFOs.  Normally, as soon as =

the FIFO has been read once by gnuplot, it is deleted.  It would be=20
possible to keep the FIFO around for possible repeated reads, but this=20
would defeat the purpose of the FIFO (which was to enable Gnuplot.py to=20
know when it is safe to discard old data).

As for a workaround, you can go back to using temporary files as a=20
default by going to the gp_*.py file specific to your platform (e.g.,=20
gp_unix.py or gp_macosx.py) and changing the option "prefer_fifo_data" =
to 0.

Michael

--=20
Michael Haggerty
mh...@al...





-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Gnuplot-py-users mailing list
Gnu...@li...
https://lists.sourceforge.net/lists/listinfo/gnuplot-py-users

Nadav Horesh wrote:

> Under linux I can not use gnuplot's mouse interaction ((un)set grid, 
> (un)zoom, etc.). It looks like gnuplot reread the data file on every 
> operation, thus it conflicts with the pipe interface introduced in 1.7.
>
> Any work-around (beside going back to 1.6)? 


Sorry I didn't respond earlier.  I was on vacation.

I am not familiar with the commands that you mentioned.  On what gnuplot 
version and platform are they?  Are they specific to a particular 
terminal type?

If this feature causes gnuplot.py to read the input file twice, that 
would indeed be a problem when working with FIFOs.  Normally, as soon as 
the FIFO has been read once by gnuplot, it is deleted.  It would be 
possible to keep the FIFO around for possible repeated reads, but this 
would defeat the purpose of the FIFO (which was to enable Gnuplot.py to 
know when it is safe to discard old data).

As for a workaround, you can go back to using temporary files as a 
default by going to the gp_*.py file specific to your platform (e.g., 
gp_unix.py or gp_macosx.py) and changing the option "prefer_fifo_data" to 0.

Michael

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