- This topic has 4 replies, 4 voices, and was last updated 10 years, 5 months ago by Anonymous.
May 28, 2013 at 7:08 pm #1597Anonymous
I am working on using the application pepspec to identify possible peptides that would bind to a protein of interest but am running into significant difficulties at the actual peptide generation stage.
After running anchordock with three other homologous proteins in order to generate a good estimate of the anchoring residue, I
use the anchor dock output (pdbs, cst files) as input to the pepspec application. The results that I get make no sense as it just outputs pdbfiles with the correct anchor, but with the other residues not connected to the anchor and spread out around the protein structure.
I’ve ran the pepspec demo, using the provided inputs and have gotten similar results. I guess my ultimate question is whether anyone else has experienced this? I am new to rosetta and running version 3.4, I have not been able to try this on any earlier versions yet. I have attached pictures of the pepspec output pdbs for further clarification
June 3, 2013 at 9:08 pm #8858Anonymous
Just as an update, I downgraded to Rosetta 3.3 and the same inputs have been working well. It seems like something got broken in this particular application in the upgrade
June 13, 2013 at 8:28 am #8895Anonymous
I am experiencing the same issue, for both versions 3.4 and 3.5.
Will try to use 3.3!
June 14, 2013 at 11:35 am #8899Anonymous
I can’t comment on 3.5, but dr. Chris King had sent me this patch for pepspec for 3.4 earlier, and it had fixed an issue similar to what you’re describing, so maybe try compiling with it? Do backup stuff, though.
If you’re trying it, rename the file in the attachment to pepspec.cc and replace the original pepspec.cc file, then re-compile Rosetta.
June 17, 2013 at 9:04 pm #8910Anonymous
Chris King has informed me that the issue should be fixed, and from what I can tell the fix should be included in the 3.5 release.
If you’re still having problem with pepspec with Rosetta 3.5, please provide further details, as it’s likely a different issue from the one encountered by rrphenix in Rosetta 3.4.
- You must be logged in to reply to this topic.