[Kst] [Bug 116461] getdata borks when the first field in the format file isn't (ASCII) alphabetically the first field.
matt at truch.net
Wed Nov 16 02:46:48 CET 2005
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
------- Additional Comments From matt truch net 2005-11-16 02:46 -------
On Tue, Nov 15, 2005 at 05:05:11PM -0800, Ted Kisner wrote:
> I still don't understand why you guys didn't just use my putData stuff for
> writing dirfiles- it does all of the reverse mapping from linterp/lincom/bit
> fields to the underlying RAW field. But whatever- I know from personal
> experience that sometimes everyone needs to reinvent a wheel or 3 ;-)
BLAST's dirfile writer (what became 'defile') was written when dirfiles
were invented, so it's pretty old.
> > but I
> > don't know if this convention is universal. AFAICT, kst never passes a
> > non-NULL value for in_field when calling GetNFrames, so it shouldn't care.
> I certainly have used kst to plot dirfile directories where the fields in the
> format file all have different sizes. Is this situation formally
> unsupported? In my opinion, that removes much of the usefullness of the
> dirfile format.
AFAIK (someone please correct me if I'm wrong), kst assumes that the
dirfile has a uniform number of frames, and if kst tries to read more
data than a raw field has it enters a race (and consumes all your cpu).
More information about the Kst