-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot handle $BYTEORD= 1,2 #3
Comments
Feel free to try fixing this, if not, I'll look at it in a few weeks. What instrument generated the FCS files? If they are fairly small, could you post a couple for future tests? |
Actually I just removed the thrown error and the file was read fine |
Could you send me the file? What was the byte order? Thanks
…On Fri, Apr 14, 2017 at 3:17 AM, Zander1983 ***@***.***> wrote:
Actually I just removed the thrown error and the file was read fine
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABENjWbawwDR-TgqISsjvaabVxILzamgks5rv0fDgaJpZM4M5s0e>
.
|
@Zander1983, I think this is fixed in v0.1.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For some FCS files I get the above error. I see it in the code here:
Any plans to fix this? Ill try myself
The text was updated successfully, but these errors were encountered: