bovee/Aston

Agilent MS Traces have erroneous zeros in them

Closed this issue · 1 comments

bovee commented

It appears that we're stopping parsing of the header 8 bytes early and reading a couple header values as M/Z, abundance values.

bovee commented

It looks like this got fixed sometime between v0.6.2 and commit 91b6c74 (at least there are no longer zero m/z values in the output and the header is considered to be 18 bytes; the correct value I believe). Closing as previously fixed.