https://bugs.kde.org/show_bug.cgi?id=358002
--- Comment #6 from netterfi...@astro.utoronto.ca --- Can we close the bug? On Thu, Feb 25, 2016 at 9:50 AM, Charles Savoie via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=358002 > > --- Comment #5 from Charles Savoie <cdsav...@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 netterfi...@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 > k...@kde.org > https://mail.kde.org/mailman/listinfo/kst > -- You are receiving this mail because: You are watching all bug changes.
