[Kst] ASCII data - confusion about multiple plots

[Barth Netterfield]

Yes:
the last page of the data wizard gives an option to put the curve in a plot
that already exists.
The curve creation dialog has an option to put the curve in a plot that
already exists.
You can do it from the command line even easier.  I can give you the
incantation if you can't clean it from kst2 --help.

cbn





On Wed, Feb 3, 2016 at 6:36 PM, Daniel Miller <dmiller at vitalconnect.com>
wrote:

> hmmm... well, I prefer lines to points in kst2; the plots with points are
> sort of hard to utilize, but I'll take a look at it and see what it looks
> like.
>
> Alternately, is there some way to input three data files, but have them
> plotted on one plot??  I haven't really seen that in the manual either...
>
>
> On Wed, Feb 3, 2016 at 3:33 PM, Barth Netterfield <
> netterfield at astro.utoronto.ca> wrote:
>
>> As you have sort of figured out, kst's data source model will want you to
>> have 3 different ascii files in this case.
>>
>> But, if you just want to plot points, and not lines, you can use NaN as
>> your bad data marker.
>>
>> On Wed, Feb 3, 2016 at 6:30 PM, Daniel Miller <dmiller at vitalconnect.com>
>> wrote:
>>
>>> I have kst2 working with single plot stream... that works very nicely.
>>> At this point, I'm using space as separator between fields.
>>>
>>> However, we have a couple of data streams which contain multiple data
>>> (x, y, z); in this situation, what our data would look like is ( timestamp,
>>> data), but the data would be one of { data_x, data_y, data_z }.  In other
>>> words, the data stream that I receive from the hardware, delivers data_x,
>>> data_y, data_z in separate messages, with different timestamps.
>>>
>>> I want kst2 to read this ascii data file and plot 3 separate graphs on
>>> one plot.
>>> I'm a little confused about how to do this, though;
>>>
>>> for example, say I have a line with data for data_z; this will look
>>> something like:
>>> timestamp data_z
>>> however, I want one file to contain data for all three streams, so I'm
>>> guessing I need to have empty fields for the not-relevant data; maybe
>>> something like:
>>> timestamp unused_x unused_y data_z
>>> timestamp unused_x data_y unused_z
>>> etc...
>>>
>>> So first off, I probably have to use a different separator rather than
>>> space for separator; but even with comma, I still have a problem; for
>>> example:
>>>
>>> timestamp, 0, 0, data_z
>>> timestamp, 0, data_y, 0
>>>
>>> Except that in some cases, 0 is valid data; I *think* I need some way to
>>> represent "invalid data" in the unused fields.
>>>
>>> Is this understandable??  How do I handle this??
>>> Dan Miller
>>>
>>> _______________________________________________
>>> Kst mailing list
>>> Kst at kde.org
>>> https://mail.kde.org/mailman/listinfo/kst
>>>
>>>
>>
>>
>> --
>> C. Barth Netterfield
>> University of Toronto
>> 416-845-0946
>>
>>
>> _______________________________________________
>> Kst mailing list
>> Kst at kde.org
>> https://mail.kde.org/mailman/listinfo/kst
>>
>>
>
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst
>
>


-- 
C. Barth Netterfield
University of Toronto
416-845-0946
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kst/attachments/20160203/868ecaa2/attachment.html>