Fileformats supported by SigBrowser
Signal Source Files
Every file with optional, arbitrary header, containing 16bit signed integer sample data in up to 8 channels can serve as a signal source if the channels are stored in an interlaced manner. That means the first 16bit represent the first sample of channel 1, followed by the 16 bit of the first sample of each channel 2 to n, then comes the same again but for the second sample of each channel and so on.
Cluster Report Files
These files have to be generated by your own tools. Afterwards they can be loaded by SigBrowser. They contain a list of activations, also called firing points, which are grouped into clusters. Every item of this list contains four 32bit integer values as follows:
| offset of n-th (1..N) item [bytes] | type (32 bit) | significance |
|---|---|---|
| 512 + (n-1)*16 + 0 | integer | cluster ID |
| 512 + (n-1)*16 + 4 | unsigned integer | start sample (0...) |
| 512 + (n-1)*16 + 8 | unsigned integer | end sample (0...) |
| 512 + (n-1)*16 + 12 | unsigned integer | quality |
These items don't have to be sorted according to the start sample
value but loading a sorted list is many times faster than loading an unsorted list (linear versus
non-polynomial behaviour).
Prepended to the first item are 512 bytes containing a 0-terminated C-like string which
should contain the filename and path of the original signal source. SigBrowser ignores this string currently.
Signal Profiles
.spr Files get generated by SigBrowser to store the block
reduced signal. Have a look at csignalrepresenter.h in the distribution
tar-ball for details. First comes a header as defined by struct signal_property_t.
Then follow 2*V blocks, V beeing the number of channels to be visualized. Each block contains
16bit signed integer data representing either the maximum or minimum values of the blocks. This
data gets generated during a block reduction of the original signal source.