Re: [spctools-discuss] readmzXML, tandem, and comet fail with files larger than 2 GB

Thanks for the response Jimmy. I had compiled comet and the whole tpp pipeline in a 64-bit environment (CENTOS GNU/Linux 7 both with gcc 4.8.3 and gcc 6.0.0) and the problem persisted. Just to verify, I downloaded the recent binaries and source for comet (2015021) and tried them, but the problem

Re: [spctools-discuss] readmzXML, tandem, and comet fail with files larger than 2 GB

Thanks, Jimmy! On Mon, Oct 12, 2015 at 2:42 PM, Jimmy Eng wrote: > Actually not only was the indexOffset off but the scan offsets were off > too. For this particular file, the offsets go bad at scan 38348, likely > where the file hits the 2GB size. > > 2147400855 >

Re: [spctools-discuss] readmzXML, tandem, and comet fail with files larger than 2 GB

Actually not only was the indexOffset off but the scan offsets were off too. For this particular file, the offsets go bad at scan 38348, likely where the file hits the 2GB size. 2147400855 2147431719 2147457995 3 3 3 3 3 On Mon, Oct 12, 2015 at 2:28 PM, Jimmy

Re: [spctools-discuss] readmzXML, tandem, and comet fail with files larger than 2 GB

I'll reply on-list to give some closure to this thread for anyone interested in the problem. I asked Daniel to send me one of his >2GB mzXML files to take a look at myself. If it wasn't a Windows 32-bit binary issue, I suspected that the problem wasn't with Tandem, Comet or the TPP tools (as I

[spctools-discuss] readmzXML, tandem, and comet fail with files larger than 2 GB

I've recently noticed some failures when using comet and xtandem! from TPP to search some centroided DDA files generated by qtofpeakpicker. These failures were all associated with files > 2GB. I was able to reduce the file size by increasing the threshold which then lead to readmzXML, tandem,

Re: [spctools-discuss] readmzXML, tandem, and comet fail with files larger than 2 GB

Daniel, The issue you're seeing might be due to TPP windows programs compiled as 32-bit binaries. The first thing I'd try is grabbing a 64-bit binary of one of the tools to see if that fixes things. You can grab a 64-bit Comet binary from its SourceForge download site if you want to test this.