Supporting .0 files from ALPHA FTIRs #24
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So, I happened to get my hand on a packet capture between OPUS and an ALPHA II...
During a scan, OPUS will poll for
.0
files that represent a scan made by the hardware.As far as I know, no tool out there including
opusFC
parses this specific "Raw 0" file.I'm sharing this so that others can possibly have a look and chime in to complete what I started. I do not have a copy of OPUS and don't want to dig any further myself.
Some notes:
Unsure about the meaning of each one, however.
0x01
, this one is0x40
. If it's0x00
, this one is the same.ADC is interferogram data. No idea what XA is for.