You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we only mark a peptide as problematic if it has no outgoing or incoming junctions. One could imagine this being a user-set threshold so that pVACvector would also mark peptides with 1,2,..,x number of incoming or outgoing junctions as problematic. This parameter would influence the likelihood of success (since more problematic junctions would now be tested with a spacer/trimming) at the cost of runtime.
The text was updated successfully, but these errors were encountered:
Found some old notes and wanted to get them into github - this seemed like the right place, as it's generally about "how to optimize pVACvector"
Right now, the default workflow is something like this:
calculate all possible junctional epitopes
if no solution is found, add next spacer, check again (loop)
if no solution is found from all spacers, start trimming back peptides
As a next pass improvement, we could probably:
calculate all possible junctional epitopes
construct the best possible vector candidate
identify any junctions that fail, hammer on just them (add spacers, trim) until a solution is found
if no solution is found, pick the next best vector candidate that lacks the problematic junctions, repeat 3. (or if some threshold of tries is reached, we could fail and output the problematic peptides as described in this issue)
With the updates I recently made to pVACvector (5.0.0 release) to implement @chrisamiller suggestions above a number of invalid junctions threshold should no longer be necessary.
However, we can further improve on the update by doing the following (a variation of the last point in Chris' comment above):
Implement a threshold that controls how many peptides are ok to be removed from the final solution
If a solution with all peptides can't be found, start by iterating over each peptide, removing it from the graph and seeing if that leads to a solution. Output all solutions found that way.
Repeat this process and progressively remove more peptides up to the limit defined in the threshold
susannasiebert
changed the title
Implement a "number of invalid junctions" threshold for pVACvector
Implement a "number peptides that can be removed" threshold for pVACvector
Dec 18, 2024
Right now we only mark a peptide as problematic if it has no outgoing or incoming junctions. One could imagine this being a user-set threshold so that pVACvector would also mark peptides with 1,2,..,x number of incoming or outgoing junctions as problematic. This parameter would influence the likelihood of success (since more problematic junctions would now be tested with a spacer/trimming) at the cost of runtime.
The text was updated successfully, but these errors were encountered: