-
Notifications
You must be signed in to change notification settings - Fork 44
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
Save to fcs? #13
Comments
I wasn't planning on adding support, but would happily merge any pull requests that add support for exporting fcs files. It's not very difficult to do -- you basically have to "reverse" the reading step If you're interested in giving it a try I'd recommend reading the FCS 3.0 specification. You can use numpy built-ins to write the numeric data and then pre-pend the relevant header information to the file. Then if the FCS reader can read the file it'll probably be readable by most other software |
Should it be 3.0 or 3.1? |
I think either works -- the specifications are mostly backwards compatible if i remember correctly |
Has this feature been implemented? I would love to use it! |
Nope -- we're open to PRs if you're interested in implementing it :) |
Note that there is fcswrite (https://github.com/ZELLMECHANIK-DRESDEN/fcswrite/). It isn't feature complete (pull-requests welcome), but it should already be sufficient for most applications. |
Hello,
I've been using your module and it is great. I was wondering if you plan to support saving back to fcs format, or if you have any recommendations for how to do this.
The text was updated successfully, but these errors were encountered: