[Kst] Re: reading ASCII files / KST command line options

Brisset, Nicolas Nicolas.Brisset at eurocopter.com
Mon Jan 31 11:09:19 CET 2011


> thank you for your fast response. Meanwhile I got the command line
> version to work. The problem is more or less the available
documentation.
OK, good that you got it working.
 
> I checked out the repository to have a look at the source and voila,
> there I found under design specs a document describing the command
line
> options for the 2.02 Version as well as all the documentation required
> for the reader plug in. By searching the documents I found that the
> order the options are given, matters. This is a little unusual so.
First
> the datafile and then the options in the right order. (-n in front tof
> the plot definitions).
Well, as I said earlier I don't use the command line so much. I'm rather
a datawizard user, and then I reload files. But it's good that you've
found it, and sending the answer to the list may help other people in
the future. Until maybe at some point the command line is improved.

> But on top of this you have to set the default settings for the reader
> in a way that it can read the file without error. This means you have
to
> set the  delimiter, the data start line, the comment symbol's and the
> line where the headers are as the default settings. Otherwise the
reader
> fails and no data are available. Unfortunately there are no command
line
> options to specify all that.
Yes, I suspected something like that. Nice that you managed to make it
work. Hopefully you can arrange for all files to have the same
formatting, otherwise it'll be difficult indeed.

> In my opinion the ASCII reader is to intollerant on the format.
Well, we've been working on that a lot (even lately) and it can
principally read any format, at least the ones I've seen so far. The
only thing that we may still improve in my opinion is an "auto-detect"
option, but that sounds very tricky. I'd rather make it so that we can
always indicate the format when we need it...

> The ".kst" file seems to be a real bug.
Yes, if you change the full path in the .kst to that of the new
location, it works. It looks like when using a relative path, the format
options are not used correctly. As they should be parsed from the .kst,
it is a hint at the fact that probably we use the settings from
QSettings correctly (they are stored under the full path of the
datafile, or use default values if the specific file is not found) but
there is an issue in reading the settings from the xml. We'll
investigate.
 
> Anyway for more complex automation it would be nice that onealso could
> specify a script on the command line to run. This would be the most
> powerful and flexible way for automation since the program generating
> the data could also generate the script for post processing and
> displaying the data.
Scripting is on the roadmap. Kst 1.x can do it, and 2.x should as well.
But right now, it has not been implemented and it is not guaranteed that
it will be compatible with the scripting available in 1.x.

Nicolas 


Eurocopter Deutschland GmbH
Sitz der Gesellschaft/Registered Office: Donauwoerth
Registergericht/Registration Court: Amtsgericht Augsburg HRB 16508
Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: Dr. Lutz Bertling
Geschaeftsfuehrung/Board of Management:
Dr. Wolfgang Schoder, Vorsitzender/CEO; Friedrich-Wilhelm Hormel; Ralf Barnscheidt

CONFIDENTIALITY NOTICE 

This communication and the information it contains is intended for the addressee(s) named above and for no other persons or organizations. It is confidential and may be legally privileged and protected by law. The unauthorized use, copying or disclosure of this communication or any part of it is prohibited and may be unlawful. 
If you have received this communication in error, kindly notify us by return e-mail and discard and/or delete the communication. Thank you very much. 
It is possible for e-mails to be intercepted or affected by viruses. Whilst we maintain virus checks on our e-mails, we accept no liability for viruses or other material which might be introduced with this message. 



More information about the Kst mailing list