Re: [spctools-discuss] COMET searches with QExactive data

2013-04-01 Thread Dave Trudgian
Jimmy, Thanks for that info. Sounds great. I'll proceed based on the knowledge that'll be available. Cheers, DT On Monday, April 1, 2013 4:43:40 PM UTC-5, Jimmy Eng wrote: > > Dave, > > Mike Hoopmann implemented a nice fix for searches using small bins. The > sources current in Comet SourceF

Re: [spctools-discuss] COMET searches with QExactive data

2013-04-01 Thread Jimmy Eng
Dave, Mike Hoopmann implemented a nice fix for searches using small bins. The sources current in Comet SourceForge trunk should be fully functional. One new parameter entry is titled "use_sparse_matrix" (see Comet version 2013.01 params in link below) which controls whether or not the sparse mat

Re: [spctools-discuss] COMET searches with QExactive data

2013-04-01 Thread Dave Trudgian
Hi Philip, Sorry to drag up an old thread, but I wondered if you had info about the effects on results of limiting Comet memory usage by using a large bin, vs using the 64-bit binary and small bin? We are primarily working with QExactive data here. I was thinking of adding Comet to our pipeli

Re: [spctools-discuss] COMET searches with QExactive data

2013-01-17 Thread Jimmy Eng
I just emailed you off-list regarding the x64 binary. On Thu, Jan 17, 2013 at 4:56 AM, Philip Brownridge < philip.brownri...@gmail.com> wrote: > Hello Jimmy, thank you very much for your quick reply! You're completely > correct about the fragment bin value, when I ran Comet (thank you for name >

Re: [spctools-discuss] COMET searches with QExactive data

2013-01-17 Thread Philip Brownridge
Hello Jimmy, thank you very much for your quick reply! You're completely correct about the fragment bin value, when I ran Comet (thank you for name guidance) using the LTQ settings it worked fine! When I ran it on the high resolution settings with task mamager on, I saw that I was getting the c

Re: [spctools-discuss] COMET searches with QExactive data

2013-01-16 Thread Jimmy Eng
Philip, I'm guessing you're specifying a small "fragment_bin_tol" value for the high-res ms/ms spectra. This causes Comet (not all capitalized) to use a ton of memory and you're just running out of memory. On the following UWPR SEQUEST page, there's a table correlating a set of fragment_bin_tol

[spctools-discuss] COMET searches with QExactive data

2013-01-16 Thread Philip Brownridge
Hello all, please can I apologise if I have posted this in the wrong group, but I can't find a COMET group and there are other COMET postings here so I hope someone can help me! I'm trying to use some QExactive data with Comet and I keep getting either a calloc error message or a message saying