LOC56985 method: Difference between revisions

From MDWiki
Jump to navigationJump to search
No edit summary
No edit summary
Line 11: Line 11:


==Structure==
==Structure==
A structural similarity search using the DALI server (Holm & Sander, 1996) identified structural homologs of 2nxf.  These results were then analysed using ClustalX (Larkin, et al., 2007) for any conserved sequences that may provide vital information about the binding sites or sequences essential to the fold of the protein. CASTp (Dundas, Ouyang et al, 2006) and Pymol (DeLano Scientific LLC, 2007) were used for visualising the protein’s secondary and tertiary structure as well as the possible bindings sites.  Both CATH (Orengo, Michie, Jones, Jones, Swindells, & Thornton, 1997) and SCOP (Murzin, Brenner et al, 1995) databases were used to identify and characterise the structure of the protein; LIGPLOT (Wallace, Laskowski, & Thornton, 1995) was used to generate schematic diagrams of the ligand-protein interactions at the binding site.  
A structural similarity search using the DALI server (Holm & Sander, 1996) identified structural homologs of 2nxf.  These results were then analysed using ClustalX (Larkin, et al., 2007) for any conserved regions in the sequence that may provide vital information about the binding sites or sequences essential to the fold of the protein. CASTp (Dundas, Ouyang et al, 2006) and Pymol (DeLano Scientific LLC, 2007) were used for visualising the protein’s secondary and tertiary structure as well as the possible bindings sites.  Both CATH (Orengo, Michie, Jones, Jones, Swindells, & Thornton, 1997) and SCOP (Murzin, Brenner et al, 1995) databases were used to identify and characterise the structure of the protein; LIGPLOT (Wallace, Laskowski, & Thornton, 1995) was used to generate schematic diagrams of the ligand-protein interactions at the binding site.  





Revision as of 14:08, 4 June 2008

Evolution

BLAST

A sequence similarity search was performed using the human orthologue of the protein 2nfx, the hypothetical protein LOC56985. This was performed through the use of blast program, BLASTP, (Altschul, Gish et al, 1990) that had been saved onto a CD in late April. Thus results could only have come from data present within the database before that day. That is the results may have been very similar but may not exactly match results achieved through a BLAST search on the NCBI (National Centre for Biotechnology Information) website. Only the highest 60 results (based on their E values) from the initial sequence search were used. For the purpose of creating a phylogenetic tree, any double up of species were removed, unless considered significant.

CLUSTAL

The selected sequences were aligned by the use of the CLUSTALX program (Larkin, et al., 2007), which is a global alignment program. From here any sequences that had extremely large gaps were also deleted. When a reasonable alignment was produced, the aligned sequences were used to form a phylogenetic tree. The tree was also bootstrapped and trees and bootstrap values were visualised using the program TreeView (Page, 1996).

Structure

A structural similarity search using the DALI server (Holm & Sander, 1996) identified structural homologs of 2nxf. These results were then analysed using ClustalX (Larkin, et al., 2007) for any conserved regions in the sequence that may provide vital information about the binding sites or sequences essential to the fold of the protein. CASTp (Dundas, Ouyang et al, 2006) and Pymol (DeLano Scientific LLC, 2007) were used for visualising the protein’s secondary and tertiary structure as well as the possible bindings sites. Both CATH (Orengo, Michie, Jones, Jones, Swindells, & Thornton, 1997) and SCOP (Murzin, Brenner et al, 1995) databases were used to identify and characterise the structure of the protein; LIGPLOT (Wallace, Laskowski, & Thornton, 1995) was used to generate schematic diagrams of the ligand-protein interactions at the binding site.


Abstract | Introduction | Results | Discussion | Conclusion | Method | References

Back To Main hypothetical protein LOC56985 page