Hi everyone,
I'm a relatively new user of Labkey and encountered an error during a search using chymotrypsin as the digesting enzyme. I've noticed Labkey automatically set <note label="protein, cleavage site" type="input">[YWFM]|{P}</note>. The error log said to use [FLMWY]|{P} for chymotrypsin which I did but then it said "The enzyme [FLMWY]|{P} was not found". Please see attached files and check if I set the parameters wrong. Any help is much appreciated.
Cheers,
Trevor |
|
jeckels responded: |
2014-11-11 12:25 |
Hi Trevor,
It looks like Tandem2XML may have changed it definition of chymotrypsin in more recent versions. We can likely update our definition to match (though we'll need to check for potential incompatibilities with other tools), but here's something you can try as a workaround:
Delete the record for the failed job in the Data Pipeline job list in the web server.
Delete the failed search result files by deleting the directory "C:\Program Files\LabKey Server\files\MS2\@files\Trev\Data\xtandem\Chymo CAM A niger PME2"
Edit the XML file that defines the enzyme directly (thus bypassing the check that's showing the error dialog message). Open "C:\Program Files\LabKey Server\files\MS2\@files\.labkey\protocols\xtandem\Chymo CAM A niger PME2.xml" (or a similarly named/located file) and edit the "protein, cleavage site" to "[FLMWY]|{P}"
Launch a new search using that saved protocol.
Please let me know if this works.
Thanks,
Josh |
|
t s loo responded: |
2014-11-11 13:33 |
Hi Josh,
Thank you for replying, I'm surprised no one has reported this bug earlier =-O
I've tried your workaround but it seemed Labkey still did the check and responded: "Error: The enzyme '[FLMWY]|{P}' was not found." I've also started a new protocol from scratch with the same result. Does this mean I have to wait till you guys tested and updated the definition before any searches with chymotrypsin can be done?
Cheers,
Trevor |
|
jeckels responded: |
2014-11-17 16:52 |
Hi Trevor,
I'm sorry the workaround didn't bypass the check. I've been able to reproduce the same behavior.
The challenge here is that different tools (and in this case, different versions of the same tool) have different definitions of the enzymes. I've updated our side to work with their variant, but unfortunately it won't be available until version 15.1 is ready.
I've opened this bug to track it:
https://www.labkey.org/issues/home/Developer/issues/details.view?issueId=21971
Thanks,
Josh |
|
|
|