[Kst] getdata patch
tskisner.public at gmail.com
Fri Jan 6 21:00:20 CET 2006
Another note: if we combine things, we need to decide how to handle the
varying number of frames issue. libdirfile allows fields to have different
numbers of frames. getdata/kst assume that all fields have the same number
of frames on disk, and that a "special field" is used to determine that
number and maintain synchronous data frame writing (frames are written to
this field last).
I suggest doing something like this:
1. have 2 different "getNFrames" functions. One returns the number of frames
for the "special" field, and one returns the number of frames for a specific
field. This way, both configurations can be supported.
2. In the case of data synchronizing, the user will be responsible for
writing to the "special" field last (using putData, etc).
On Friday 06 January 2006 11:33, Barth Netterfield wrote:
| Without commenting on this particular patch....
| This brings up an idea that Ted has championed for a while now: that
| getdata should be its own library (as is cfitsio, HDF, etc etc) and not a
| part of kst.
| The advantage is that we could have a single libDirfile svn tree somewhere,
| and would avoid the problem of forking that has been a problem in the past,
| and people could easily install libDirfile without installing kst (of
| course, why would someone want to do such a horrible thing?) and could
| install kst without installing dirfiles.
| The disadvantage is that it would mean one more install for people who want
| dirfile access through kst.
| Any thoughts on this?
| On January 6, 2006 01:52 pm, Matthew D Truch wrote:
| > Attached is a patch I'd like to apply to getdata (the 'library' for the
| > dirfile reader), but I'm going to ask here first. It modifies no code
| > that kst uses; it merely adds a new function to getdata that lets you
| > close all the open files getdata has for a given dirfile. I'd like to
| > apply it just to make things easy in keeping kst's getdata in sync with
| > the getdata we use in other blast analysis programs.
| > The reason I want the close function is: when you read files over nfs,
| > often there are errors (nfs sucks). Generally this causes the file to
| > become stale; a re-read will continue to fail, unless you close and
| > reopen the file first. With GetDataClose(), you can close all the
| > files, and the next time you try and read them, GetData will open and
| > read for you.
| Kst mailing list
| Kst at kde.org
More information about the Kst