This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
filtering [2012/03/02 15:49] 132.168.72.131 créée |
filtering [2012/03/02 16:01] (current) 132.168.72.131 |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Filtering ====== | ====== Filtering ====== | ||
+ | [[principle|Back to concepts]] | ||
==== Master Protein Filter ==== | ==== Master Protein Filter ==== | ||
Line 10: | Line 10: | ||
:!: **In a protein group the FIRST protein which matches the rules composition will be set as master.** \\ | :!: **In a protein group the FIRST protein which matches the rules composition will be set as master.** \\ | ||
:!: If no protein in the protein group matches the rules composition, the old one is kept. \\ | :!: If no protein in the protein group matches the rules composition, the old one is kept. \\ | ||
- | :!: If the new master don't match some ambiguous peptides (because they belonging only to the old master) they will be deleted without asking (in contrary of manual master protein changing). | + | :!: If the new master don't match some ambiguous peptides (because they belonging only to the old master) **they will be deleted without asking** (in contrary of manual master protein changing). |
+ | |||
+ | In the case peptides belonging to other protein groups, as relevant/significative, will be deleted , a Warn message is reported in log : | ||
+ | Example of log Message : | ||
+ | 14:06:07,279 [AWT-EventQueue-0] WARN PGPAssocation - WARNING : Changing master from B0NIL1_EUBSP to CAT_ACIAN will cause supression of peptides. | ||
+ | 14:06:07,294 [AWT-EventQueue-0] INFO PGPAssocation - Delete 5025 (QFLHIYSXDVACYGENLAYFPK) | ||
+ | 14:06:07,294 [AWT-EventQueue-0] INFO PGPAssocation - Delete 5204 (QFLHIYSXDVACYGENLAYFPK) | ||
+ | 14:06:07,294 [AWT-EventQueue-0] WARN PGPAssocation - ********** ----- Peptide QFLHIYSXDVACYGENLAYFPK belonged to Q93F28_SHIFL as Significative !! | ||
+ | |||
+ | This shouldn't occurred often as same peptide belonging to multiple portein groups have similar score and properties so they should have be passed as ambiguous in all protein groups ... | ||
=== The rules === | === The rules === | ||
Line 32: | Line 41: | ||
As seen below the composition part of the filter window show you the translation of the composition you maked, to verify you don't do mistakes. | As seen below the composition part of the filter window show you the translation of the composition you maked, to verify you don't do mistakes. | ||
+ | |||
{{:userguide:master-filter_composition-window.png|}} | {{:userguide:master-filter_composition-window.png|}} | ||
+ | |||
+ | |||
=== Examples === | === Examples === | ||
Line 102: | Line 114: | ||
**Nota** : in that example, apply the Score & Rank filter with parameters to only kept rank 1 peptides would have lead to mark the second one as ambiguous, in contrary of the Single Match per Query Filter | **Nota** : in that example, apply the Score & Rank filter with parameters to only kept rank 1 peptides would have lead to mark the second one as ambiguous, in contrary of the Single Match per Query Filter | ||
- |