[Veusz-discuss] [PATCH] support stacked super- and sub-scripts

2010-12-20 Par sujet Benjamin K. Stuhl
Hi all,
  I recently discovered Veusz and I am finding that I like it much more
than my old standby Origin. (Especially Veusz's support for
alpha-blending!) I've been hacking on it a bit today to make it more
useful for my application, and I've got a couple of patches to submit.
^_^

This patch modifies the text renderer so that multiple super- or
subscripts get rendered stacked rather than staggered; it makes things
like X^{(g)}_{lm} render properly.

I've attached the patch, since I don't trust my webmail to not mangle it.

Regards,
-- BKS

veusz-multiscript.patch
Description: Binary data
___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


[Veusz-discuss] [PATCH] support multi-line texts for plot keys

2011-01-12 Par sujet Benjamin K. Stuhl
Hi all,
  Here's a patch which enhances the Key widget to do proper layout when
the key texts are longer than one line. The layout system tries to keep
the overall box as small as possible while still using as many columns
as the user requested. (IOW, it will stretch out the layout to fill the
last N columns even if everything could be fit into fewer. This is
important if, say, you have 4 items and you want 4 columns, even though
one of the items is two lines tall and so all four items would fit into
a 2x3 layout...) I also added a setting to control whether the key
symbol is aligned to the first line of the text, the center, or the last
line of the text.

The patch passes some manual torture testing, including a few pathological
orderings that I could think up. I've attached a sample file which shows
the new layout abilities.

I've attached the patch, since I don't trust my webmail to not mangle it.

Regards,
-- BKS


veusz-multiline-key-texts.patch
Description: Binary data


keytest.vsz
Description: Binary data
___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] [PATCH] support multi-line texts for plot keys

2011-01-12 Par sujet Benjamin K. Stuhl
And here's a version of the patch with the debugging prints removed...

Regards,
-- BKS

On Wed, January 12, 2011 13:10, Benjamin K. Stuhl wrote:
 Hi all,
   Here's a patch which enhances the Key widget to do proper layout when
 the key texts are longer than one line. The layout system tries to keep
 the overall box as small as possible while still using as many columns
 as the user requested. (IOW, it will stretch out the layout to fill the
 last N columns even if everything could be fit into fewer. This is
 important if, say, you have 4 items and you want 4 columns, even though
 one of the items is two lines tall and so all four items would fit into
 a 2x3 layout...) I also added a setting to control whether the key
 symbol is aligned to the first line of the text, the center, or the last
 line of the text.

 The patch passes some manual torture testing, including a few pathological
 orderings that I could think up. I've attached a sample file which shows
 the new layout abilities.

 I've attached the patch, since I don't trust my webmail to not mangle it.

 Regards,
 -- BKS



veusz-multiline-key-texts.patch
Description: Binary data
___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] Suggestions about Datetime datasets and the Picker

2011-09-16 Par sujet Benjamin K. Stuhl

On 9/12/2011 12:38 PM, Jeremy Sanders wrote:

On 12/09/11 18:20, mimisa...@gmail.com wrote:

In my opinion it would be great if
1. The point picker could recognize DateTime datasets and show the point
coordinates in ISO data format.
2. One could use ISO data format to set the values of axes min and max.
3. One could decide from which dataset the picker picks the points.


I've just put together a patch for the first part. It seems to work ok.

BKS - have you got a better way to get this into your picker code?


Hmm... what you've got would certainly work, but I'm not so fond of 
putting presentation into the Dataset. (I think it's much better to keep 
presentation in the presentation layers...)


However, while it'd be a more invasive change, it might make sense to 
add a 'usage' field to DatasetBase, to go alongside 
DatasetBase.datatype. DatasetBase.usage would be e.g. 'abstime', 
'reltime', 'numeric' and could be used to guide point 2 as well

as the picker presentation. Alternatively, DatasetDateTime.datatype
could be changed, but that would probably have other fallout.


The second point would definitely be good. The axis should also
autodetect when dates are plotted rather than have to be set like that.
It should then display min and max as dates.

I wonder what would be the correct user interface for the 3rd idea.
Seems quite tricky... Maybe some sort of drop down menu from the pick
button to enable/disable datasets. At the moment you should just be able
to hide the datasets you don't want to pick from.


Maybe a decent interface for it is to add a 'Pick within currently 
selected widgets' tool?


Regards,
-- BKS

___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] (no subject)

2011-11-08 Par sujet Benjamin K. Stuhl
On Tue, November 8, 2011 02:49, Jeremy Sanders wrote:
 If you want to use the source, on linux you can use a package manager to
 download the dependencies. On Windows and Mac OS it is more difficult

 You can install Python from a binary, and install the numpy modules from a
 binary too.

 You can get the Qt binary distribution from the nokia website, then build
 SIP - instructions here
 http://www.riverbankcomputing.co.uk/static/Docs/sip4/index.html - then get
 PyQt - http://www.riverbankcomputing.co.uk/static/Docs/PyQt4/html/index.html

Alternatively, on Windows you can install python(x,y) 
(http://code.google.com/p/pythonxy/),
which includes PyQt, numpy, (and a lot more), and optionally a compiler so you 
can build more
python extensions.

Regards,
-- BKS

___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] Future development plans

2011-12-11 Par sujet Benjamin K. Stuhl
On Sat, December 10, 2011 09:16, Jeremy Sanders wrote:
[snip]
 2. Data imports - possible formats
   - HDF, JSON, XML, VO-table, Origin, IDL, XLS, OpenOffice, ..., any
 more common ones?
   - Improve existing import filters?
   - Some sort of data import wizard like openoffice

   Extra formats could be fairly easy if implemented as plugin. Fancier
 UI requires plugin interface improvement or full import.

A big one: Matlab .mat files. The most recent versions of MATLAB save as HDF5 
-- so that would
definitely be useful -- but older versions are a custom format. scipy.io has 
support for loading
them. (And also support for loading IDL .sav files, which might also be useful.)

Also, is there interest in accumulating a large set of (more or less) obscure 
import plugins? I
have one which I wrote for the log files generated by Stanford Research Systems 
RGA units, and
I've been thinking about writing one for .s1p/.s2p files which are some kind of 
a de facto
standard for network analyzers.

 3. More widgets (medium to hard)
   - Projections of spherical data, aitoff, etc., useful for maps, etc. - More 
 specialised widgets?
 - pie

 4. Improvements of widgets (easy to hard)
   - Log polar, colored points for polar, ternary...

Some way to draw error bands on a function or fit plot? Also, either possibly 
exposing more error
analysis functionality in the fit widget or perhaps as a plugin which 
optionally _creates_ a fit
widget?

 5. Communication with other programs
   - D-Bus - I'm examining this currently
   - SAMP - for virtual observatory
   - anything else? - maybe whatever is used for embedding in widnows - 
 C/C++/Fortran/Perl
external API?
   - Better clipboard support

 6. Improve LaTeX support

 7. Improve data editing
   - spreadsheet mode to examine multiple datasets
   - select multiple datasets in dataset browser

 8. Useful new plugins - easy to medium - please write or suggest some
   - FFT, smoothing, binning, filtering...

FFT would definitely be useful. Another (easy) one is a sorting plugin, i.e. 
sort N dependent
datasets and one independent dataset by the independent dataset. (Right now, if 
you want to merge
multiple datasets, the only decent way is by writing python code; with a sort 
plugin you could
just catenate and then sort -- although it might be worth having a merge plugin 
that does just
that, as well.)

 9. Expand existing plugins to work properly on dates, 2D, etc. (easy to 
 medium)

 10. New dataset types, such as bundled 1D datasets. Probably hard.

 11. Speed improvements.

 12. User interface improvements.

Regards,
-- BKS



___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] exporting data from Veusz

2012-01-10 Par sujet Benjamin K. Stuhl
On Tue, January 10, 2012 11:04, George wrote:
 I've been using Veusz for some time now and I'm thrilled with its 
 capabilities!

 One particularly useful feature in my opinion is the data set manipulation.
 However once I've loaded some data and manipulated it the way I want, I 
 haven't
 been able to figure out how to export the manipulated data sets in a text
 format. The reason why I would like to do this is because some of the people 
 I'm
 working with don't use Veusz, so I would like to be able to give them tab
 delimitted data files containing some of my manipulated data sets so that they
 can plot them using other plotting programs. Is there such an export feature? 
 If
 there is, I wasn't able to find it.

Hi George,
  I don't know of an export _command_, as such, but it should be easy to do 
from the Veusz
python console. Since Veusz is built on top of numeric python (numpy), all of 
the numpy
I/O routines are available. A good reference page for them is
http://docs.scipy.org/doc/numpy/reference/routines.io.html

As an example, if you want to export the array 'data1' to 'filename.txt', you 
could run

 savetxt('filename.txt', GetData('data1')[0])

which would save the values (though _not_ the error bars, unfortunately) to 
'filename.txt'.
Saving the error bars as well takes just a bit more work, since Veusz stores 
the data
and error bars as separate numpy.ndarrays:

 # first we combine the data and error bar columns into a single 
 numpy.ndarray:
 d1 = column_stack([ v for v in GetData('data1') if v is not None])

 # then we write it to a file
 savetxt('filename.txt', d1)

I hope this helps!

Regards,
-- BKS

___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] linear fit

2012-04-30 Par sujet Benjamin K. Stuhl
On Mon, April 30, 2012 13:10, Jeremy Sanders wrote:
 On 28/04/12 11:48, Antonio wrote:
 Hello everybody,
 I checked Veusz linear fit against a certified data set coming from NIST:
 Statistical Reference Datasets http://www.itl.nist.gov/div898/strd/ .
 In particular,  the first one I used was the Norris dataset you could find 
 here:
 http://www.itl.nist.gov/div898/strd/lls/data/Norris.shtml .
 Maybe I did something weird and stupid  but the line fit does not look like 
 the
 data plot and coefficients are pretty different from certified ones.

 I checked the dataset against gnuplot, gnumeric, extrema, labplot, SSP, PSPP,
 ... and the fit looks allright with them.

 Thanks - I didn't get the line to fit initially, but that appears to be
 because it doesn't have any uncertainties associated with it. Veusz
 assumes 5% errors if there are no uncertainties, which doesn't work in
 some cases with the minimisation procedure. Probably because the 5%
 errors give lots of weight to the values near zero. I haven't tested
 whether pyminuit does a better job (veusz supports this as an optional
 fitting module).

I loaded your test.vsz in a pyminuit build and get similar results to you:
the fit is very strange if I include the points near zero with relative error 
bars,
but works fine using either the fixed uncertainties data set or if I just 
exclude the
points with x  1. So I agree that this is indeed related to the default 
assumed 5%
uncertainty.

Regards,
-- BKS

___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] Error function

2012-07-20 Par sujet Benjamin K. Stuhl

On 7/20/2012 4:56 AM, Jeremy Sanders wrote:

On 20/07/12 10:20, Paul Cardinaels wrote:

Hi all,

I have been using Veusz for some years now and it has always helped me
in producing high quality graphs for my reports.
Now that I have started my graduation project in fluid dynamics I have
come across some problems that depend on the error function:
http://en.wikipedia.org/wiki/Error_function

Is there a quick/easy way to use it in Veusz? I can't seem to find it.


If you're using Veusz from source (or in a linux distribution), you can
get it from scipy if you have scipy installed (import from scipy.special
in the custom definitions dialog). If you're using the binary
distribution, there are some hacks to get veusz to see an installed
version of scipy (I can provide some hints if you're interested).

There's a simpler alternative, which is to use a python module to
compute erf (to some precision). Here's some code, adapted from
http://stackoverflow.com/questions/457408/is-there-an-easily-available-implementation-of-erf-for-python

It seems to work for me (check, please!). Put it in a .py file. Go to
the custom definition dialog, add a custom import. The problem might be
that veusz can't find this file and you need to set the PYTHONPATH
environment variable to find it. I should add an option to allow
explicit paths to be included, or to set PYTHONPATH. You can set it to
be loaded automatically in the options dialog with a custom definitions
file.

I think it could be compressed to one line and entered as a function
instead, if anyone feels like rewriting it.

Jeremy

---

import numpy as np

def erf(x):
 # save the sign of x
 sign = np.sign(x)
 sign[ sign == 0 ] = 1
 x = np.abs(x)

 # constants
 a1 =  0.254829592
 a2 = -0.284496736
 a3 =  1.421413741
 a4 = -1.453152027
 a5 =  1.061405429
 p  =  0.3275911

 # AS formula 7.1.26
 t = 1.0/(1.0 + p*x)
 y = 1.0 - (a5*t + a4)*t) + a3)*t + a2)*t + a1)*t*np.exp(-x*x)
 return sign*y # erf(-x) = -erf(x)


Here's a one-liner form I've used occasionally (derived, ultimately, 
from Numerical Recipes chapter 6.2):


AddCustom(u'function', u'erf(z)', u'([1 - t * exp( -z*z -  1.26551223 + 
t * ( 1.2368 + t * ( 0.37409196 +  t * ( 0.09678418 +  t * 
(-0.18628806 +  t * ( 0.27886807 +  t * (-1.13520398 +  t * ( 1.48851587 
+  t * (-0.82215223 +  t * ( 0.17087277)) for t in (1.0 / (1.0 + 
0.5 * abs(z)),)])[0] * (2*(z = 0) - 1)')


Regards,
-- BKS

___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] using numeric data for labels

2013-09-23 Par sujet Benjamin K. Stuhl

On 9/23/2013 5:38 PM, Joseph Xu wrote:

I'm trying to make a bar chart with numeric labels at the top, kind of
like this:

http://www.dplot.com/barchart/barchart3_h600.png

I tried to do this by adding an additional x-y plot with hidden
markers and the bar chart length for both the y position and the
labels. However, it seems like you can't use numeric data sets for
labels. I tried some other things, like creating a dataset using
str(y) for the expression, but that fails also. Is there any way to
hack around this?


Hi Joseph,
  Your idea about creating a dataset using str(y) is a good one, it 
just takes a bit more typing at the veusz console command line. If your

numeric dataset is named 'y', you could create a text label dataset by

SetDataText('y_labels', [ str(v) for v in GetData('y')[0] ])

for example. I hope this helps with your goal!

Regards,
-- BKS


___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] HDF5 support badly needed

2013-12-06 Par sujet Benjamin K. Stuhl

On 12/6/2013 2:18 PM, Jeremy Sanders wrote:

I didn't really understand your point about storing in HDF5 before. I
see you would like some sort of vsz hdf5 saved file. I can see that
might work. However, I can't see a nice way of storing the document tree
in HDF5 file, unless it's encoded in XML. I'll read up a bit more about
HDF5.


Why not keep the document tree format the same python text that it is 
now and just store it as a string in the HDF5 file? The only objects in 
the save file that are large enough to benefit from HDF5 storage are the 
datasets themselves, and adding a new create Veusz dataset from a 
dataset in this HDF5 file command is easy enough. So the hypothetical

.v5z binary format might be an HDF5 structure with

/veusz -- the .vsz stored as a string
/datasets/* -- actual storage for the datasets

Thoughts?

-- BKS

___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] Feature Request

2014-03-05 Par sujet Benjamin K. Stuhl

On 3/5/2014 9:57 PM, Gerrit Barrere wrote:

I'm new on this subscriber list and don't know the etiquette -- I hope
this is the right way to start a discussion about a potential new
feature.  Please let me know if this should be done differently.

Veusz is a fabulous program.  It's extremely powerful and aesthetically
beautiful (but you all already know that).  I have written a program to
configure the raw data output from my HP impedance analyzer into a form
Veusz will import, including data and labels, so I can get beautiful
plots of the instrument output to put into my lab reports (example
attached).  Everything is working perfectly except for one thing.

I would like to see a widget for a data trace marker as an element of
a Veusz xy graph.  This would be a line or marker which can be slid back
and forth to read out the data at the line position.  The readout could
be placed anywhere on the graph.  I'm attaching a screen shot of an
application which has this type of function.  The vertical line can be
dragged back and forth and the horizontal line follows the data.  The
dialog box shows the X and Y data.


Hi Gerrit,
  Welcome to the list, and this is certainly the appropriate place to 
ask questions or make feature requests. In this particular case, it may 
be that Veusz actually already has part of the feature you are looking 
for: the crosshair icon on the toolbar (in between the mouse arrow and 
the zoom-in icon in the default layout) is a point picker tool. It reads 
back the index and value of the selected point in the status bar and 
supports navigation using the left/right arrow keys to scan along one 
curve and up/down to jump between curves. What it does not do -- but 
certainly could be added as a widget -- is give some permanent display 
on the plot canvas. For now, you'd need to draw the crosshairs yourself 
using a pair of lines and a text label if you want to highlight a 
specific point in your lab report.


Regards,
-- BKS

___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] Data import

2014-07-06 Par sujet Benjamin K. Stuhl
Perhaps the proper way to present it is as an asymmetric error bar? That 
is, treat 0.05 as 0 (+ 0.05) (-0)?


Since Veusz supports independent positive and negative errors, it should 
not be too difficult to create an input plugin which handles that 
transformation.


Regards,
-- BKS

On 7/6/2014 11:30 AM, Henrik Rydberg wrote:

Thanks for your reply!

Well, I think your suggestions are good, but what I want to achieve is:
- presentation of the numeric value eventhough it is 0.05
- label or marker on those results so that the viewer knows it is below that
level of quantification
- ...but most important that an actual sample is taken and examined at that
level of quantification!

Hence:
NAN interpolate - you wouldn´t know sample exist and is quantified
NAN skip - as above
Treat as zero - incorrect data, result could be up to limit of
quantification
Treat as max/min - ?
Treat as marker - maybe!

By using a split dataset in my example one could use set2 for plotting all
values and set1 as markers, that is  would be printed next to the
datapoint at the 0.05 level so that you could see:
1. sample is taken
2. value is verified to be below 0.05
3. we know that value is not 0.05, but denoted  and hence below limit of
quantification

regards
/Henrik




___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss




___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] Suggestion: gap format

2015-05-14 Par sujet Benjamin K. Stuhl
On 5/14/2015 8:36 PM, Tim Channon wrote:
 Unless I have missed something an omission from Veusz is the ability to
 simply draw polylines, a line plotter.
 
 I draw outline geographic maps using gle (which needs minor script
 assistance) and with gnuplot (which doesn't).
 
 Veusz is very close to achieving the same effect.
 
 All that is needed is being able to distinguish between move to and line
 to.

Hi Tim,
  If what you mean by move to is that there should be no line between
the previous point and the target point, all you need to do in Veusz is
insert a coordinate pair containing at least one NaN. (Written, nicely
enough, as nan or NaN.) So:

x1 y1
x2 y2
nan nan
x3 y3
x4 y4

will have lines connecting pts. 1  2 and 3  4, but not 2  3. It might
take a tiny bit of scripting to insert the NaNs where you want them. Or
writing an input plugin which automatically handles the blank lines as a
pair of NaNs.

Regards,
--BKS


___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] TIF export with LZW/ZIP compression

2015-05-14 Par sujet Benjamin K. Stuhl
On 5/14/2015 11:15 AM, Mike Statkus wrote:
 Many thanks to Jeremy for the outstanding plotting tool!
 
 Is it intended that TIFF export produces images without compression? 16*12 
 cm figure at 300 dpi (1800*1400 pixels) is saved by Veusz export as a 10 
 Mb TIFF, which is reduced to 300 Kb TIF after opening with Photoshop and 
 saving as TIF with LZW compression enabled. Unfortunately, I haven't found 
 an option in Veusz 1.23 to turn on LZW or ZIP compression in TIF files.

You're right, Veusz does not seem to turn on TIFF compression. The good
news is that it should be trivial to fix, the QImageWriter just needs
  writer.setCompression(1)
called on it. I'll try to put together a pull request next week if
Jeremy doesn't do a fix first.

We might also want to set
  writer.setOptimizedWrite(true)
  writer.setProgressiveScanWrite(true)
for new Qt versions that will support them; this improves the JPEG
output file sizes. (See https://bugreports.qt.io/browse/QTBUG-20075,
which was merged for 5.5.)

Regards,
--BKS


___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] Automatic export

2015-05-14 Par sujet Benjamin K. Stuhl
On 5/14/2015 3:15 PM, Henrik Rydberg wrote:
 Thank you for the explanation and for the one and only plotting software I
 always come back to. Veusz is amazing!
 
 I just thought, since the reload function have some kind of timer maybe it
 would not be so hard to add kind of a tick box used together with reload
 like export on reload...since the export plugin could already be set up
 with desired settings and overwrite without prompt.

Hi Henrik,
  To some extent, this is possible to do using a script run in Veusz --
it's probably not a _supported_ usage, but it works. The key is that you
can import PyQt4 from the scripting command line and it works. If you
open the example Help-Example documents-fit and paste the following
lines into the command prompt, you'll see that the data points update
once a second, and so does the fit:

def timerFn():
  d, symerr, poserr, negerr = GetData('y')
  d *= 1.1
  SetData('y', d, symerr=symerr, poserr=poserr, negerr=negerr)
  Action('fit', '/page1/graph1/fit1')

from PyQt4 import QtCore
timer = QtCore.QTimer()
timer.timeout.connect(timerFn)
timer.start(1000) # run once per second

The contents of timerFn can probably be almost anything that you could
type at the Veusz command line; I've tested GetData(), SetData(), Set(),
Action(), and Export() and they all work. (Although print() doesn't
work, I checked that.) In particular, you could do

def timerFn():
  ReloadData()
  Export('myplot.eps') # and customize your settings

and it should work. If this works for you, please let me know. (Though
as I said, this is probably totally unsupported and may crash randomly
-- though since QTimer is fired through the event loop, it should be
much more stable than e.g. trying to fire off a QThread.)

Regards,
--BKS

___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] Automatic export

2015-05-15 Par sujet Benjamin K. Stuhl
On May 15, 2015 1:34 PM, Henrik Rydberg henryd0...@gmail.com wrote:

 Works like a charm, exactly what I wanted. Not only an amazing pieece of
 software, but also real support. Thanks a lot!

 /Henrik

 (How do I stop the running script?)

Glad that it's working for you! You can stop it by running

timer.stop()

at the command line.

Regards,
--BKS
___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] TIF export with LZW/ZIP compression

2015-06-02 Par sujet Benjamin K. Stuhl
Hi Martin,
  Just to let you and the list know: Jeremy has pulled my Git branch
with the improvement for TIFF compression and a (unrelated) bugfix to
get PNG compression working again. Both will be in the next release of
Veusz, or can be gotten now if you build from the development tree.

Regards,
--BKS

On 5/15/2015 3:55 AM, Martinus WERTS wrote:
 Thanks to all!
 
 We had a similar question for the PNG format. I guess/hope the proposed
 change will also enable compression for PNG.
 
 Best wishes,
 Martin
 
 On 15/05/2015 03:16, Benjamin K. Stuhl wrote:
 On 5/14/2015 11:15 AM, Mike Statkus wrote:
 Many thanks to Jeremy for the outstanding plotting tool!

 Is it intended that TIFF export produces images without compression?
 16*12
 cm figure at 300 dpi (1800*1400 pixels) is saved by Veusz export as a 10
 Mb TIFF, which is reduced to 300 Kb TIF after opening with Photoshop and
 saving as TIF with LZW compression enabled. Unfortunately, I haven't
 found
 an option in Veusz 1.23 to turn on LZW or ZIP compression in TIF files.
 You're right, Veusz does not seem to turn on TIFF compression. The good
 news is that it should be trivial to fix, the QImageWriter just needs
writer.setCompression(1)
 called on it. I'll try to put together a pull request next week if
 Jeremy doesn't do a fix first.

 We might also want to set
writer.setOptimizedWrite(true)
writer.setProgressiveScanWrite(true)
 for new Qt versions that will support them; this improves the JPEG
 output file sizes. (See https://bugreports.qt.io/browse/QTBUG-20075,
 which was merged for 5.5.)

 Regards,
 --BKS


 ___
 Veusz-discuss mailing list
 Veusz-discuss@gna.org
 https://mail.gna.org/listinfo/veusz-discuss
 
 
 ___
 Veusz-discuss mailing list
 Veusz-discuss@gna.org
 https://mail.gna.org/listinfo/veusz-discuss


___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] Plot shapes using axes coordinates

2015-08-05 Par sujet Benjamin K. Stuhl
On 8/5/2015 8:34 AM, Michael Clerx wrote:
 I'm using Veusz to create 2D scatterplots for a large number of
 x-coordinates. Because the x-axis is subdivided into different regions
 I'd like to add some visual reference showing that, for example, the
 interval [127, 150] is segment 1, while the interval [159, 178] is
 segment 2. I was hoping to use shapes for this, but it seems I can
 only specify their widths as a fraction of the figure size.

 Can anyone think of a clever way to accomplish this?

Hi Michael,
  If you add a line shape, you can change its Position mode from
relative to axes and the Mode to point-to-point. In that case,
you can specify the exact axes-units coordinates for the start and end
points of the lines, so you could have say a line running from (127, 5)
to (150, 5) to indicate the segment, or whatever may be appropriate for
your data. I hope this helps with what you want to accomplish!

Regards,
--BKS

___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] bar chart

2016-02-22 Par sujet Benjamin K. Stuhl
Hi Birger,
  If you put NaN instead of zero, Veusz will automatically break the
xy-plot lines at each missing value. Is that closer to what you want?

Regards,
Ben

On 2/22/2016 1:11 PM, Birger Ilau wrote:
> Hi,
>
> I'm plotting multiple groups of data and there are different number of
> values in each group. In the data fail, I put 0 to the positions of
> missing values to groups that have fewer values than others. But I
> don't really want empty spaces on my chart. I don't know a better way
> to do this.
> Can anyone help me out, please?
>
> All the best,
>
> Birger 
>
>
> ___
> Veusz-discuss mailing list
> Veusz-discuss@gna.org
> https://mail.gna.org/listinfo/veusz-discuss


___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] problem with error bars end size

2016-05-12 Par sujet Benjamin K. Stuhl
Hi Carla,
  One thing to check is under the main settings for the xy widget,
towards the bottom, is the error bar style. It defaults to just a line
with no ends; you'll need to change it to something else for the end
size to matter.

If that doesn't fix your issue, could you post a file showing the problem?

Regards,
--BKS

On 5/12/2016 7:47 AM, carla wrote:
> Hi, 
> I am using veusz v1.24 for creating a 2D plot.
> I am doing a graph with points. I have a problem with the error
> bars of points. The end size does not change. Actually error bars are
> shown as bars without an end. 
> Sorry, but I did not find any previous post with this issue.
> Is there any way to fix it?
>
> Thanks,
> Carla   
>
>
> ___
> Veusz-discuss mailing list
> Veusz-discuss@gna.org
> https://mail.gna.org/listinfo/veusz-discuss


___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss


Re: [Veusz-discuss] X-Y plots

2016-09-05 Par sujet Benjamin K. Stuhl
Hi Martin,
  Do I understand correctly that you are looking for a way to automate
adding widgets to a plot?

If that's what you want to do, this is where Veusz's Python console
shines. You have a couple of options. You can use the Add() function to
create new widgets, for instance by

>>> To('/page1/plot1') # or whatever widget path you want to add things to
>>> for xds, yds in [('atomic_number' + str(n), 'concentration' +
str(n)) for n in xrange(1, 56)]:
>>>Add('xy', xData=xds, yData=yds)

or you can use the command line to create new, combined datasets

>>> SetData('atomic_number_combined', [ GetData('atomic_number' +
str(n))[0][0] for n in xrange(1, 56) ])
>>> conc = [ GetData('concentration' + str(n))[0][0] for n in xrange(1,
56) ]
>>> SetData('concentrations_combined', [ c[0][0] for c in conc ],
symerr=[ c[1][0] for c in conc ])

and then create one xy plot manually.

The Veusz manual at http://home.gna.org/veusz/docs/manual.html has a
good description of the general Python API; to see what settings and
subsettings a widget can take, create one of those widgets and look at
the mouse-over tool-tip for each setting to see the setting's Pythonic name.

I hope this helps!

Regards,
Ben

On 9/5/2016 3:14 PM, Martin Valencia wrote:
> Dear Jeremy,
> …dear friends in the Veusz blog,
>
> I am trying to make a X-Y plot for chemical concentrations of rock
> samples. The y axis is the concentration in ppm and the x axis is for
> the chemical elements (55 in total). I am doing the plot adding the
> samples one by one, but the problem is that I have a dataset of more
> than 100 samples. Is there a way to plot all them a at time, instead
> of one by one? I would appreciate much your help…
>
> Thank you.
> Regards,
>
> /Martín/
> ___
> /Dr. Martín Valencia Moreno///
> /Investigador Titular A/
> /Estación Regional del Noroeste/
> /Instituto de Geología, UNAM/
> /L.D. Colosio S/N y Madrid, Col. Los Arcos/
> /Hermosillo, Sonora 83240, México/
> /Tel: (662) 217 50 19; Fax: (662) 217 53 40/
> /martin.valen...@unam.mx /
> /http://www.geologia-son.unam.mx//
>
>
>
>
>
> ___
> Veusz-discuss mailing list
> Veusz-discuss@gna.org
> https://mail.gna.org/listinfo/veusz-discuss



___
Veusz-discuss mailing list
Veusz-discuss@gna.org
https://mail.gna.org/listinfo/veusz-discuss