how_to:changetypicalprotein
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
how_to:changetypicalprotein [2010/02/04 08:49] 132.168.74.230 créée |
how_to:changetypicalprotein [2010/03/16 14:52] (current) 132.168.73.247 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== How to change typical protein ====== | ====== How to change typical protein ====== | ||
| + | Filtering can be done on 1 or more User Context. Once desired contexts are selected, you can | ||
| + | * Right-click on contexts in MSI database ans select Algorithms -> Change typical protein | ||
| + | * Or choose MS Identification –> Context –> Algorithms -> Change typical protein | ||
| - | Use rules combinations. In order to use same feature as IRMa, the user should be able to: | + | The following window will appear |
| + | |||
| + | {{:how_to:changetypical.png|}} | ||
| + | |||
| + | Typical protein modification is based on rules combinations, in the same way as in IRMa. | ||
| + | |||
| + | User should : | ||
| * specify a set of rules defining | * specify a set of rules defining | ||
| + | * a name (which will be referenced in rules compositions) | ||
| * the field on which the rule will be applied : accession or description | * the field on which the rule will be applied : accession or description | ||
| * the test operation which will be executed : starts with / ends with / contains or don't contains | * the test operation which will be executed : starts with / ends with / contains or don't contains | ||
| * the text to search in the given field (Case sensitive) | * the text to search in the given field (Case sensitive) | ||
| * specify one or more rules compositions | * specify one or more rules compositions | ||
| + | * use rule name (**without any other characters such as < or "**) in logical composition | ||
| ===== Example 1 - unique rule composition ===== | ===== Example 1 - unique rule composition ===== | ||
| - | User will want to select as typical, protein which has | + | User wants to select as typical, protein which has |
| * its description starting with "sp" | * its description starting with "sp" | ||
| * or its description starting with "tr" and its accession ending with "_HUMAN" | * or its description starting with "tr" and its accession ending with "_HUMAN" | ||
| Line 17: | Line 28: | ||
| To do this the user will have to create 3 rules : | To do this the user will have to create 3 rules : | ||
| - | 1. R1: description starts with "sp" | + | - ''rule1'' : description starts with "sp" |
| - | 2. R2: description starts with "tr" | + | - ''rule2'' : description starts with "tr" |
| - | 3. R3: accession ends with "_HUMAN" | + | - ''rule3'' : accession ends with "_HUMAN" |
| - | and creates the following rule composition: R1 or (R2 and R3).\\ | + | and creates the following rule composition: ''rule1 or (rule2 and rule3 )''.\\ |
| When running the module, for each PutativeProtein the typical protein will be set to the first one which respects the rule composition constraint. | When running the module, for each PutativeProtein the typical protein will be set to the first one which respects the rule composition constraint. | ||
| Line 27: | Line 38: | ||
| In this example, the user will preferentially wants to select as typical a protein which has its description starting with "sp".\\ | In this example, the user will preferentially wants to select as typical a protein which has its description starting with "sp".\\ | ||
| - | If no protein respects that constraint then user will want to select as typical a protein which has its description starting with "tr" and its accession ending with "_HUMAN".\\ | + | If no protein respect that constraint then user will want to select as typical a protein which has its description starting with "tr" and its accession ending with "_HUMAN".\\ |
| - | If we uses the same rules as in example 1 (R1, R2 and R3), the typical protein to choose will be one (the first) which respect R1 and if none is found the new typical protein should respect rules composition (R2 or R3).\\ | + | If we uses the same rules as in example 1 (''rule1'' , ''rule2'' and ''rule3'' ), the typical protein to choose will be one (the first) which respect ''rule1'' and if none is found the new typical protein should respect rules composition ''(rule2 or rule3)''.\\ |
| To do this, the user will have to create 3 rules : | To do this, the user will have to create 3 rules : | ||
| - | 1. R1: description starts with "sp" | + | - ''rule1'' : description starts with "sp" |
| - | 2. R2: description starts with "tr" | + | - ''rule2'' : description starts with "tr" |
| - | 3. R3: accession ends with "_HUMAN" | + | - ''rule3'' : accession ends with "_HUMAN" |
| create two rules compositions: | create two rules compositions: | ||
| - | 1. C1 : R1 | + | - C1 : ''rule1'' |
| - | 2. C2 : R2 or R3 | + | - C2 : ''rule2or rule3'' |
| and order rules compositions by priority | and order rules compositions by priority | ||
| - | * C1 then C2 | + | * C1 will be specified in prority 1 field then C2 in priority 2 field |
how_to/changetypicalprotein.1265269773.txt.gz · Last modified: 2010/02/04 08:49 by 132.168.74.230
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
