> We need a file format for the data files.
>
> magic string
> format version number
> data, including user specified strings for signal names
> checksum
> allow for comments (e.g '#' )
> allow for demand paging (how?)
Here is one way to do it:
/ogp_pci_analyzer/data/testrun23/part10000
# OGP PCI ANALYZER DATASET FORMAT 0.1
# CHECKSUM 123456789
# sample number, clock, data0, data1, data2, ...
10000,0,0,0,1,0,1,1,1, ...
10001,1,0,0,1,0,1,1,1, ...
10002,0,0,0,1,0,1,0,1, ...
10003,1,0,0,1,0,1,1,1, ...
/ogp_pci_analyzer/data/testrun23/part11000
# OGP PCI ANALYZER DATASET FORMAT 0.1
# CHECKSUM 123456783
# sample number, clock, data0, data1, data2, ...
11000,0,0,0,1,0,1,1,0, ...
11001,1,0,0,1,0,1,1,0, ...
11002,0,0,0,1,0,1,0,0, ...
11003,1,0,0,1,0,1,1,0, ...
Advantages:
simple
human readable
We instantly have a way to look at the data
using more, emacs, vi ...
This will not be the preferred viewing format
for most of us (if anyone), but at least it
is possible, and doesn't require any special software.
The data can be manipulated with the usual grep,
cut, paste, sed, awk, perl, and so on.
handles demand paging
If a single file is desired, cat the data together
and redo the checksum.
Note: This would be a format for the files on disk. I am *not* suggesting
this format for transferring data from the OGD to the support machine.
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
