gnuplot-py-users Mailing List for Gnuplot.py

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
>