Dear Peter, Thank you for your response. Yes. it is a custom binary file type. I attached the sample binary files. humanK562C_d2.splib is the original one. temp.splib is the uploaded and corrupted one. For definition in Galaxy, I just simply inherit the binary.Binary. The definition is below: In Python script: class Splib( binary.Binary ): """ Class describing a spectral library (splib)""" file_ext = "splib" I did not add the sniffer but specify the file format manually in the page of "get data". Best Regards, HU Yingwei 2012/2/25 Peter Cock <p.j.a.cock@googlemail.com>
On Fri, Feb 24, 2012 at 4:03 PM, Yingwei HU <husince@gmail.com> wrote:
Dear all,
I found one of my binary files was corrupted after its uploading through "Get data'. I used editplus to check its hex code and found some "0D" is changed to "0A" and also one byte is lost. May I ask how to solve this problem?
Thank you for your help.
Best Regards, HU Yingwei
There has been a similar discussion on the archives - those hex codes are ASCII carriage return and line feed characters, meaning the changes were made assuming the file was plain text to standardize the new lines.
What file type is it, and how is this defined on your Galaxy? i.e. Is it a custom binary file type?
Peter