seq stands for sequence identifier, it’s only meant to identify if there’s a miss in the sequence so it’s not relevant for the db itself and you noticed there might have been lots of misses at some point. I also used it inconsistently as some tests have tne same seq for group of samples. Also unfortunately some sample misses might not be due to uwb but the the rf report channel that is not reliable due to the real time need but could be improved.
Yes, I’ll definitely be adding more samples and scale to large databases where I simply let it capture for a longer time (within the next week). Just keep in mind the range dist measure is a simplistic estimation taken from the examples and far from showing the best uwb accuracy (no calib, no compensation yet)
I’m also workining on the extraction of the channel impulse response accumulator.
For info, and if you want, you can define even your own python database capture script and I can run it for you, here’s the python repo that I linked on the announcement topic
or a direct link to the db capture funtion