Dear Jeremy,

Thank you very much for answering.
1. Your proposal for adding a field in parameters of importplugin seems
good.
I would imagine simply a field called "number of header lines".
It would take the first line/column for the data names and skip the rest of
the lines/columns in header and start reading data just after header.
I can also send a sample of the dataset I usually use if you want. To say
honestly, this kind of data is quite common format in engineering field as
it fits easily with excel.
2. Thank you, I will try. I saw in previous discussions an other person had
same problem. Launching Veusz from source is working, so I will try what
you've written with compiled version.
3. I have an other question for you, sorry... The data I want to import are
timeseries. It means for each data channels, I have a time channel related.
The way mdf is made allows several data groups corresponding to one time
channel (in total several time channels for several data groups). From my
trials, the dataset2D is not corresponding to these data, the dataset1D
either. Do you think I should implement a new data class to be managed by
Veusz specifically for timeseries ?

Aymeric

2010/11/20 Jeremy Sanders <jer...@jeremysanders.net>

> aymeric rateau wrote:
>
> > 1. I was not able to load csv file with more than 1 line of comment. I
> > would say that most generally generated files from data acquisition
> > equipment (like engine bench) contain at least 2 header lines, One for
> the
> > channel name and the second for the units. I could not find a field in
> the
> > import interface to allow csv import with more than 1 line header. Would
> > it be possible to arrange this ? Ultimatively, it would be interesting to
> > consider the unit in the code to be displayed with the channel name.
>
> It's difficult to think of a way of specifying the data format of any type
> of CSV files. If anyone has a suggestion for how this might be done please
> tell me!
>
> I could add an option to only have one set of data in a column/row and to
> ignore any further text in that column.
>
> > 2. We use heavily the system INCA from ETAS company, generating MDF files
> > (binary structure file a bit like netcdf or hdf5). I developed a module
> > you could find source at following address :
> > http://code.google.com/p/mdfreader/source/browse/
> > So, I am now writing a plugin for Veusz to be able to visualize/analyse
> > recorded data.
> > I want to use Veusz in windows (compiled version) but I can not use my
> > plugin attached (located in plugin directory with dedicated mdf plugin).
> > Inside the plugin, I do a import to my mdf reader module, but during
> veusz
> > launch, this module is not found. Would you know why and how to fix this
> ?
>
> As the compiled versions has its own copy of python, any modules which are
> installed in your local python aren't seen as it doesn't know about your
> local python directory.
>
> You can try setting the PYTHONPATH environment variable to contain the
> directory of your module. This should work as long as Veusz contains its
> dependencies.
>
> Jeremy
>
>
>
> _______________________________________________
> 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

Répondre à