| Summary: | Only plots Points. Lines missing | ||
|---|---|---|---|
| Product: | [Applications] kst | Reporter: | Charles Savoie <cdsavoie> |
| Component: | plotting | Assignee: | kst |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | netterfield |
| Priority: | NOR | ||
| Version: | 2.0.8 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Sample.kst
data_raw3_test.txt attachment-21325-0.html |
||
|
Description
Charles Savoie
2016-01-14 21:51:47 UTC
I can not reproduce this. Can you please pull up a curve edit dialog on one of the curves behaving this way: -in a plot: rmb->edit Curve->... is [x] Lines selected? What color is set? What is the line width? Does changing the line width do anything? Created attachment 97544 [details] Sample.kst Here's a sample ASCII data file and Kst config file. Columns 1 & 2 have continuous data and plot just fine (lines and points). Columns 3-10 have discontinuous data, and only plots points (lines do not show). I hope this helps. Thanks, Charlie On 2/24/2016 11:23 AM, via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=358002 > > netterfield@astro.utoronto.ca changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |netterfield@astro.utoronto. > | |ca > > --- Comment #1 from netterfield@astro.utoronto.ca --- > I can not reproduce this. > > Can you please pull up a curve edit dialog on one of the curves behaving this > way: > -in a plot: rmb->edit Curve->... > > is [x] Lines selected? > What color is set? > What is the line width? > Does changing the line width do anything? > Created attachment 97545 [details]
data_raw3_test.txt
This is working as designed: Ascii files are 1 frame per line, so all fields are assumed to be at the same sample rate. The ascii reader config option allows for missing data to be interpreted as a NaN, replaced with the previous value, or be interpreted as 0. NaN represents a hole in the data, so no line is drawn to it. If a data point has NaNs on both sides of it, then there will be no line drawn to it. We could consider adding the option to interpolate NaNs either in the ascii reader or in the curve dialog. Or we could consider adding the option to have a 'frame' be multiple lines, allowing for variable numbers of samples per frame in ascii. Alternatively, consider using a data source that natively handles variable numbers of samples per frame (eg, dirfiles). Thank you for your clarification. Much appreciated. On 2/24/2016 6:00 PM, via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=358002 > > --- Comment #4 from netterfield@astro.utoronto.ca --- > This is working as designed: > > Ascii files are 1 frame per line, so all fields are assumed to be at the same > sample rate. > > The ascii reader config option allows for missing data to be interpreted as a > NaN, replaced with the previous value, or be interpreted as 0. > > NaN represents a hole in the data, so no line is drawn to it. If a data point > has NaNs on both sides of it, then there will be no line drawn to it. > > We could consider adding the option to interpolate NaNs either in the ascii > reader or in the curve dialog. > > Or we could consider adding the option to have a 'frame' be multiple lines, > allowing for variable numbers of samples per frame in ascii. > > Alternatively, consider using a data source that natively handles variable > numbers of samples per frame (eg, dirfiles). > Created attachment 97554 [details] attachment-21325-0.html Can we close the bug? On Thu, Feb 25, 2016 at 9:50 AM, Charles Savoie via KDE Bugzilla < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=358002 > > --- Comment #5 from Charles Savoie <cdsavoie@gmail.com> --- > Thank you for your clarification. Much appreciated. > > On 2/24/2016 6:00 PM, via KDE Bugzilla wrote: > > https://bugs.kde.org/show_bug.cgi?id=358002 > > > > --- Comment #4 from netterfield@astro.utoronto.ca --- > > This is working as designed: > > > > Ascii files are 1 frame per line, so all fields are assumed to be at the > same > > sample rate. > > > > The ascii reader config option allows for missing data to be interpreted > as a > > NaN, replaced with the previous value, or be interpreted as 0. > > > > NaN represents a hole in the data, so no line is drawn to it. If a data > point > > has NaNs on both sides of it, then there will be no line drawn to it. > > > > We could consider adding the option to interpolate NaNs either in the > ascii > > reader or in the curve dialog. > > > > Or we could consider adding the option to have a 'frame' be multiple > lines, > > allowing for variable numbers of samples per frame in ascii. > > > > Alternatively, consider using a data source that natively handles > variable > > numbers of samples per frame (eg, dirfiles). > > > > -- > You are receiving this mail because: > You are the assignee for the bug. > _______________________________________________ > Kst mailing list > Kst@kde.org > https://mail.kde.org/mailman/listinfo/kst > Yes. I am satisfied with your answer. Thank you On 2/25/2016 10:23 AM, via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=358002 > > --- Comment #6 from netterfield@astro.utoronto.ca --- > Can we close the bug? > > On Thu, Feb 25, 2016 at 9:50 AM, Charles Savoie via KDE Bugzilla < > bugzilla_noreply@kde.org> wrote: > >> https://bugs.kde.org/show_bug.cgi?id=358002 >> >> --- Comment #5 from Charles Savoie <cdsavoie@gmail.com> --- >> Thank you for your clarification. Much appreciated. >> >> On 2/24/2016 6:00 PM, via KDE Bugzilla wrote: >>> https://bugs.kde.org/show_bug.cgi?id=358002 >>> >>> --- Comment #4 from netterfield@astro.utoronto.ca --- >>> This is working as designed: >>> >>> Ascii files are 1 frame per line, so all fields are assumed to be at the >> same >>> sample rate. >>> >>> The ascii reader config option allows for missing data to be interpreted >> as a >>> NaN, replaced with the previous value, or be interpreted as 0. >>> >>> NaN represents a hole in the data, so no line is drawn to it. If a data >> point >>> has NaNs on both sides of it, then there will be no line drawn to it. >>> >>> We could consider adding the option to interpolate NaNs either in the >> ascii >>> reader or in the curve dialog. >>> >>> Or we could consider adding the option to have a 'frame' be multiple >> lines, >>> allowing for variable numbers of samples per frame in ascii. >>> >>> Alternatively, consider using a data source that natively handles >> variable >>> numbers of samples per frame (eg, dirfiles). >>> >> -- >> You are receiving this mail because: >> You are the assignee for the bug. >> _______________________________________________ >> Kst mailing list >> Kst@kde.org >> https://mail.kde.org/mailman/listinfo/kst >> The behavior is as intended and is appropriate. |