01-11-2024 01:34 PM
We don't care about the program executable. How did you generate the pictured data? I assume using your "controller.vi" program from your first message.
01-11-2024 02:23 PM
This is what I got when I ran the code.
01-11-2024 04:23 PM
This is what I had when I run the code. Earlier message was sent from my lab's PC.
01-11-2024 04:37 PM
Arrrggghhh! NO PICTURES, please! Save the bytes you are getting in a (binary) file, and attach the file! We need to see the data, not some (unknown) program spewing out largely unreadable characters.
Bob Schor
01-11-2024 04:46 PM
File attached.
01-11-2024 04:48 PM
I was prevented from attaching the .txt file on here so I copied and pasted in word attached but they appear modified in the word version
01-11-2024 05:35 PM
You can zip any file and attach it here.
01-11-2024 05:59 PM
zipped file attached
01-13-2024 09:07 AM
Yes! Real data! Patterns begin to emerge!
What can you tell us about this stream of bytes? Is this a "snapshot" of streaming data, by which I mean "data are coming in (at some rate) and this is an arbitrary sample of 337 continuous arrays of 8-byte records"? I can see some periodicity in it, perhaps suggesting two "cycles" of about 160 x 8 byte data. It does appear to be mainly numeric, mainly integer. Haven't tried tricks like bit-reversal, but there are some intriguing periodicities in this sample.
Some questions:
A few years back, I was handed some 9-track "computer tapes" (back in the days of CDC and DEC computers saving data on "mag tape") and was given the puzzle of deciphering what the (scientific) data were on those tapes. Fortunately, they were a mix of integer, reals (32-bit, or as we called it, "single precision", and (as we called it) "ASCII". Arrays could be recognized by the (now I don't remember if it was a 2-byte or 4-byte) header that gave the size. We managed to resurrect the data, as I recall ...
Bob Schor
01-13-2024 10:50 AM - edited 01-13-2024 11:02 AM
The data is highly repetitive with a period of 8 bytes.
The first two are mostly x0003, followed by two highly variable bytes followed by four bytes that are mostly x01000029. (very few exceptions, see below.
Two exceptions where it does not start with x0003:
and five exceptions where it does not end in x0029, but in x0028:
and two exceptions where the third group is not x0100
Obviously, we need to know much more about all this. Do you have the parsed table data for exactly the same dataset?