This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
how_to:generateamtdb [2012/02/29 09:39] 132.168.73.124 |
how_to:generateamtdb [2012/02/29 12:08] 132.168.73.124 |
||
---|---|---|---|
Line 2: | Line 2: | ||
:!: **Requirements** \\ | :!: **Requirements** \\ | ||
- | Context have to be **[[how_to:proteingrouping|grouped]]** previously. | + | * Context have to be **[[how_to:proteingrouping|grouped]]** previously. You generally apply some filtering during and/or after the protein grouping step to suppress: |
- | You may want apply some filters during this step: | + | * Reverse proteins |
- | * Reverse proteins | + | * Species with a sequence < 7 |
- | * Species with a sequence < 7 | + | * Proteins identified by only 1 species with a score < 60 |
- | * Proteins identified by only 1 species with a score < 60 | + | * **[[how_to:alignretentiontime|Retention time alignment]]** & **[[how_to:recomputeretentiontime|retention time recomputing]]** algorithms may have to be run before creating |
- | + | * Save your MSIdb | |
- | :!: **Notes** \\ | + | \\ |
- | **[[how_to:alignretentiontime|Retention time alignment]]** & **[[how_to:recomputeretentiontime|retention time recomputing]]** algorithms may have to be run before creating | + | \\ |
- | + | \\ | |
- | + | To generate a new AMT database in the MS Access format (.mdb file) from a given User context, follow these steps: | |
- | + | ||
- | To generate a new AMT database in the MS Access format (.mdf file) from a given User context, follow these steps: | + | |
{{ :amtexport_menu.png|Export a context to a new AMT database}} | {{ :amtexport_menu.png|Export a context to a new AMT database}} | ||
Line 40: | Line 38: | ||
===== AMT database model ===== | ===== AMT database model ===== | ||
- | + | When creating an AMT database (MS Access) from hEIDI, following tables are populated: | |
- | Below is the actual AMT database model showing relationships between tables in MS Access.\\ | + | |
- | + | ||
- | When exporting an AMT database from hEIDI, 5 tables are populated: | + | |
* **__Table AMT__**: species of the exported User context | * **__Table AMT__**: species of the exported User context | ||
+ | * AMT_ID: index for this AMT tag (generated) | ||
+ | * AMTMonoisotopicMass: peptide calculated mass | ||
+ | * NET: computed from peptide (aligned) retention time using the formula: NET = (rtSeconds/60 - delayMinutes) / durationMinutes | ||
+ | * PNET: | ||
+ | * MSMS_Obs_Count: | ||
+ | * High_Normalized_Score: peptide score | ||
+ | * High_Discriminant_Score: | ||
+ | * Sequence: peptide sequence | ||
+ | * msidb_peptide_match_id: peptide_match_id used in MSIdb to create this AMT tag | ||
* **__Table AMT_Proteins__**: proteins on which species match | * **__Table AMT_Proteins__**: proteins on which species match | ||
* Protein_ID: protein identifier | * Protein_ID: protein identifier | ||
Line 69: | Line 73: | ||
* context_is_saved: is the exported context has been saved to MSIdb ? | * context_is_saved: is the exported context has been saved to MSIdb ? | ||
* msidb_context_id: context identifier in the MSIdb (look at this field only if the context has been saved to MSIdb) | * msidb_context_id: context identifier in the MSIdb (look at this field only if the context has been saved to MSIdb) | ||
+ | * duration_minutes: analysis duration in minutes | ||
+ | * delay_minutes: analysis delay in minutes | ||
+ | |||
+ | :!: **Notes**: | ||
+ | * UMCs tables were populated using '[[how_to:includeumcinamtdb|Read UMCs]]' tool until hEIDI 1.12.0.\\ | ||
+ | * Since hEIDI 1.13.0, [[how_to:importumctomsidb|UMCs result files are included into MSIdb]] (instead of AMTdb) | ||
- | UMCs tables are populated when using '[[how_to:includeumcinamtdb|Read UMCs]]' tool. | ||
{{:how_to:amtexport_relationsmsaccess.png|Relationships in the AMT database (MS Access)}} | {{:how_to:amtexport_relationsmsaccess.png|Relationships in the AMT database (MS Access)}} |