Summary: Pou domain - N-terminal to homeobox domain
Pfam includes annotations and additional family information from a range of different sources. These sources can be accessed via the tabs below.
This is the Wikipedia entry entitled "POU domain". More...
The Wikipedia text that you see displayed here is a download from Wikipedia. This means that the information we display is a copy of the information from the Wikipedia database. The button next to the article title ("Edit Wikipedia article") takes you to the edit page for the article directly within Wikipedia. You should be aware you are not editing our local copy of this information. Any changes that you make to the Wikipedia article will not be displayed here until we next download the article from Wikipedia. We currently download new content on a nightly basis.
Does Pfam agree with the content of the Wikipedia entry ?
Pfam has chosen to link families to Wikipedia articles. In some case we have created or edited these articles but in many other cases we have not made any direct contribution to the content of the article. The Wikipedia community does monitor edits to try to ensure that (a) the quality of article annotation increases, and (b) vandalism is very quickly dealt with. However, we would like to emphasise that Pfam does not curate the Wikipedia entries and we cannot guarantee the accuracy of the information on the Wikipedia page.
Editing Wikipedia articles
Before you edit for the first time
Wikipedia is a free, online encyclopedia. Although anyone can edit or contribute to an article, Wikipedia has some strong editing guidelines and policies, which promote the Wikipedia standard of style and etiquette. Your edits and contributions are more likely to be accepted (and remain) if they are in accordance with this policy.
You should take a few minutes to view the following pages:
How your contribution will be recorded
Anyone can edit a Wikipedia entry. You can do this either as a new user or you can register with Wikipedia and log on. When you click on the "Edit Wikipedia article" button, your browser will direct you to the edit page for this entry in Wikipedia. If you are a registered user and currently logged in, your changes will be recorded under your Wikipedia user name. However, if you are not a registered user or are not logged on, your changes will be logged under your computer's IP address. This has two main implications. Firstly, as a registered Wikipedia user your edits are more likely seen as valuable contribution (although all edits are open to community scrutiny regardless). Secondly, if you edit under an IP address you may be sharing this IP address with other users. If your IP address has previously been blocked (due to being flagged as a source of 'vandalism') your edits will also be blocked. You can find more information on this and creating a user account at Wikipedia.
If you have problems editing a particular page, contact us at email@example.com and we will try to help.
The community annotation is a new facility of the Pfam web site. If you have problems editing or experience problems with these pages please contact us.
POU domain Edit Wikipedia article
|Pou domain - N-terminal to homeobox domain|
The acronym POU is derived from the names of three transcription factors:
- the Pituitary-specific Pit-1
- the Octamer transcription factor proteins Oct-1 and Oct-2 (octamer sequence is ATGCAAAT)
- the neural Unc-86 transcription factor from Caenorhabditis elegans.
Comparisons of POU domain genes across the animals suggests that the family can be divided into six major classes (POU1-POU6). Pit-1 is part of the POU1 class, Oct-1 and Oct-2 are members of POU2, while Unc-86 is a member of POU4. The six classes diverged early in animal evolution: POU1, POU3, POU4, and POU6 classes evolved before the last common ancestor of sponges and eumetazoans, POU2 evolved in the Bilatera, and POU5 appears to be unique to vertebrates.
There is a surprisingly high degree of amino acid sequence conservation (37%-42%) of POU homeodomains to the transcriptional regulator comS, the competence protein from the gram positive prokaryote Bacillus subtilis. Akin to the way that POU homeodomain regulators lead to tissue differentiation in metazoans, this transcription factor is critical for differentiation of a subpopulation of B. subtilis into a state of genetic competence.
POU proteins are eukaryotic transcription factors containing a bipartite DNA binding domain referred to as the POU domain. The acronym POU (pronounced 'pow') is derived from the names of three transcription factors, the pituitary-specific Pit-1, the octamer-binding proteins Oct-1 and Oct-2, and the neural Unc-86 from Caenorhabditis elegans. POU domain genes have been described in organisms as divergent as Caenorhabditis elegans, Drosophila, Xenopus, zebrafish and human but have not been yet identified in plants and fungi. The various members of the POU family have a wide variety of functions, all of which are related to the function of the neuroendocrine system and the development of an organism. Some other genes are also regulated, including those for immunoglobulin light and heavy chains (Oct-2), and trophic hormone genes, such as those for prolactin and growth hormone (Pit-1).
The POU domain is a bipartite domain composed of two subunits separated by a non-conserved region of 15-55 aa. The N-terminal subunit is known as the POU-specific (POUs) domain (InterPro: IPR000327), while the C-terminal subunit is a homeobox domain (InterPro: IPR007103). 3D structures of complexes including both POU subdomains bound to DNA are available. Both subdomains contain the structural motif 'helix-turn-helix', which directly associates with the two components of bipartite DNA binding sites, and both are required for high affinity sequence-specific DNA-binding. The domain may also be involved in protein-protein interactions. The subdomains are connected by a flexible linker. In proteins a POU-specific domain is always accompanied by a homeodomain. Despite of the lack of sequence homology, 3D structure of POUs is similar to 3D structure of bacteriophage lambda repressor and other members of HTH_3 family.
Human genes encoding proteins containing the POU domain include:
- POU2F1; POU2F2; POU2F3;
- POU3F1; POU3F2; POU3F3; POU3F4;
- POU4F1; POU4F2; POU4F3;
- POU5F1; POU5F1P1; POU5F1P3; POU5F1P4;
- POU6F1; POU6F2
- Phillips K, Luisi B (Oct 2000). "The virtuoso of versatility: POU proteins that flex to fit". Journal of Molecular Biology. 302 (5): 1023–39. doi:10.1006/jmbi.2000.4107. PMID 11183772.
- Gold, David A.; Gates, Ruth D.; Jacobs, David K. (2014-12-01). "The Early Expansion and Evolutionary Dynamics of POU Class Genes". Molecular Biology and Evolution. 31 (12): 3136–3147. doi:10.1093/molbev/msu243. ISSN 0737-4038. PMC . PMID 25261405.
- D'Souza C, Nakano MM, Zuber P (September 1994). "Identification of comS, a gene of the srfA operon that regulates the establishment of genetic competence in Bacillus subtilis". Proc. Natl. Acad. Sci. U.S.A. 91 (20): 9397–401. doi:10.1073/pnas.91.20.9397. PMC . PMID 7937777.
- Assa-Munt N, Mortishire-Smith RJ, Aurora R, Herr W, Wright PE (Apr 1993). "The solution structure of the Oct-1 POU-specific domain reveals a striking similarity to the bacteriophage lambda repressor DNA-binding domain". Cell. 73 (1): 193–205. doi:10.1016/0092-8674(93)90171-L. PMID 8462099.
- Andersen B, Rosenfeld MG (Feb 2001). "POU domain factors in the neuroendocrine system: lessons from developmental biology provide insights into human disease". Endocrine Reviews. 22 (1): 2–35. doi:10.1210/er.22.1.2. PMID 11159814.
- Petryniak B, Staudt LM, Postema CE, McCormack WT, Thompson CB (Feb 1990). "Characterization of chicken octamer-binding proteins demonstrates that POU domain-containing homeobox transcription factors have been highly conserved during vertebrate evolution". Proceedings of the National Academy of Sciences of the United States of America. 87 (3): 1099–1103. doi:10.1073/pnas.87.3.1099. PMC . PMID 1967834.
- Johnson WA, Hirsh J (Feb 1990). "Binding of a Drosophila POU-domain protein to a sequence element regulating gene expression in specific dopaminergic neurons". Nature. 343 (6257): 467–470. doi:10.1038/343467a0. PMID 1967821.
- Mathis JM, Simmons DM, He X, Swanson LW, Rosenfeld MG (Jul 1992). "Brain 4: a novel mammalian POU domain transcription factor exhibiting restricted brain-specific expression". The EMBO Journal. 11 (7): 2551–2561. PMC . PMID 1628619.
- Phillips K, Luisi B (Oct 2000). "The virtuoso of versatility: POU proteins that flex to fit". Journal of Molecular Biology. 302 (5): 1023–1039. doi:10.1006/jmbi.2000.4107. PMID 11183772.
- Klemm JD, Rould MA, Aurora R, Herr W, Pabo CO (Apr 1994). "Crystal structure of the Oct-1 POU domain bound to an octamer site: DNA recognition with tethered DNA-binding modules". Cell. 77 (1): 21–32. doi:10.1016/0092-8674(94)90231-3. PMID 8156594.
- Jacobson EM, Li P, Leon-del-Rio A, Rosenfeld MG, Aggarwal AK (Jan 1997). "Structure of Pit-1 POU domain bound to DNA as a dimer: unexpected arrangement and flexibility". Genes & Development. 11 (2): 198–212. doi:10.1101/gad.11.2.198. PMID 9009203.
This tab holds the annotation information that is stored in the Pfam database. As we move to using Wikipedia as our main source of annotation, the contents of this tab will be gradually replaced by the Wikipedia tab.
Pou domain - N-terminal to homeobox domain Provide feedback
No Pfam abstract.
Internal database links
|SCOOP:||HTH_19 HTH_3 HTH_31|
|Similarity to PfamA using HHSearch:||HTH_3 HTH_31|
External database links
This tab holds annotation information from the InterPro database.
InterPro entry IPR000327
POU proteins are eukaryotic transcription factors containing a bipartite DNA binding domain referred to as the POU domain. The acronym POU (pronounced 'pow') is derived from the names of three mammalian transcription factors, the pituitary-specific Pit-1, the octamer-binding proteins Oct-1 and Oct-2, and the neural Unc-86 from Caenorhabditis elegans. POU domain genes have been identified in diverse organisms including nematodes, flies, amphibians, fish and mammals but have not been yet identified in plants and fungi. The various members of the POU family have a wide variety of functions, all of which are related to the function of the neuroendocrine system [PUBMED:8462099] and the development of an organism [PUBMED:11159814]. Some other genes are also regulated, including those for immunoglobulin light and heavy chains (Oct-2) [PUBMED:1967834, PUBMED:1967821], and trophic hormone genes, such as those for prolactin and growth hormone (Pit-1).
The POU domain is a bipartite domain composed of two subunits separated by a non-conserved region of 15-55 aa. The N-terminal subunit is known as the POU-specific (POUs) domain (INTERPRO), while the C-terminal subunit is a homeobox domain (INTERPRO). 3D structures of complexes including both POU subdomains bound to DNA are available. Both subdomains contain the structural motif 'helix-turn-helix', which directly associates with the two components of bipartite DNA binding sites, and both are required for high affinity sequence-specific DNA-binding. The domain may also be involved in protein-protein interactions [PUBMED:1628619]. The subdomains are connected by a flexible linker [PUBMED:11183772, PUBMED:8156594, PUBMED:9009203]. In proteins a POU-specific domain is always accompanied by a homeodomain. Despite of the lack of sequence homology, 3D structure of POUs is similar to 3D structure of bacteriophage lambda repressor and other members of HTH_3 family [PUBMED:11183772, PUBMED:8156594].
This entry represents the POU-specific subunit of the POU domain.
The mapping between Pfam and Gene Ontology is provided by InterPro. If you use this data please cite InterPro.
|Molecular function||transcription factor activity, sequence-specific DNA binding (GO:0003700)|
|Biological process||regulation of transcription, DNA-templated (GO:0006355)|
Below is a listing of the unique domain organisations or architectures in which this domain is found. More...
The graphic that is shown by default represents the longest sequence with a given architecture. Each row contains the following information:
- the number of sequences which exhibit this architecture
a textual description of the architecture, e.g. Gla, EGF x 2, Trypsin.
This example describes an architecture with one
Gladomain, followed by two consecutive
EGFdomains, and finally a single
- a link to the page in the Pfam site showing information about the sequence that the graphic describes
- the UniProt description of the protein sequence
- the number of residues in the sequence
- the Pfam graphic itself.
Note that you can see the family page for a particular domain by clicking on the graphic. You can also choose to see all sequences which have a given architecture by clicking on the Show link in each row.
Finally, because some families can be found in a very large number of architectures, we load only the first fifty architectures by default. If you want to see more architectures, click the button at the bottom of the page to load the next set.
Loading domain graphics...
This family contains a diverse range of mostly DNA-binding domains that contain a helix-turn-helix motif.
The clan contains the following 256 members:AbiEi_3_N AbiEi_4 ANAPC2 AphA_like Arg_repressor ARID B-block_TFIIIC Bac_DnaA_C BetR Bot1p BrkDBD C_LFY_FLO Cdc6_C CENP-B_N Cro Crp CSN8_PSD8_EIF3K Cullin_Nedd8 CUT DDRGK DEP Dimerisation Dimerisation2 DsrD DUF1133 DUF1153 DUF1323 DUF134 DUF1441 DUF1492 DUF1495 DUF1670 DUF1804 DUF1836 DUF1870 DUF2089 DUF2250 DUF2316 DUF2582 DUF3116 DUF3253 DUF3853 DUF3860 DUF3908 DUF433 DUF4364 DUF4447 DUF480 DUF722 DUF739 DUF742 DUF977 E2F_TDP EAP30 ELL ESCRT-II Ets Exc F-112 FaeA Fe_dep_repr_C Fe_dep_repress FeoC FokI_C FokI_N Forkhead Ftsk_gamma FUR GcrA GerE GntR HARE-HTH HemN_C HNF-1_N Homeobox Homeobox_KN Homez HPD HrcA_DNA-bdg HSF_DNA-bind HTH_1 HTH_10 HTH_11 HTH_12 HTH_13 HTH_15 HTH_16 HTH_17 HTH_18 HTH_19 HTH_20 HTH_21 HTH_22 HTH_23 HTH_24 HTH_25 HTH_26 HTH_27 HTH_28 HTH_29 HTH_3 HTH_30 HTH_31 HTH_32 HTH_33 HTH_34 HTH_35 HTH_36 HTH_37 HTH_38 HTH_39 HTH_40 HTH_41 HTH_42 HTH_43 HTH_45 HTH_46 HTH_47 HTH_5 HTH_6 HTH_7 HTH_8 HTH_9 HTH_AraC HTH_AsnC-type HTH_CodY HTH_Crp_2 HTH_DeoR HTH_IclR HTH_Mga HTH_micro HTH_OrfB_IS605 HTH_psq HTH_Tnp_1 HTH_Tnp_1_2 HTH_Tnp_4 HTH_Tnp_IS1 HTH_Tnp_IS630 HTH_Tnp_ISL3 HTH_Tnp_Mu_1 HTH_Tnp_Mu_2 HTH_Tnp_Tc3_1 HTH_Tnp_Tc3_2 HTH_Tnp_Tc5 HTH_WhiA HxlR IBD IF2_N IRF KicB KORA KorB La LacI LexA_DNA_bind Linker_histone LZ_Tnp_IS481 MADF_DNA_bdg MarR MarR_2 MerR MerR-DNA-bind MerR_1 MerR_2 Mga Mnd1 Mor MotA_activ MqsA_antitoxin MRP-L20 Myb_DNA-bind_2 Myb_DNA-bind_3 Myb_DNA-bind_4 Myb_DNA-bind_5 Myb_DNA-bind_6 Myb_DNA-bind_7 Myb_DNA-binding Neugrin NUMOD1 OST-HTH P22_Cro PaaX PadR PAX PCI Penicillinase_R Phage_AlpA Phage_antitermQ Phage_CI_repr Phage_CII Phage_rep_org_N Phage_terminase Pou Pox_D5 PuR_N Put_DNA-bind_N Rap1-DNA-bind Rep_3 RepA_C RepA_N RepC RepL Replic_Relax RFX_DNA_binding Ribosomal_S19e Ribosomal_S25 Rio2_N RNA_pol_Rpc34 RP-C RPA RPA_C RQC Rrf2 RTP RuvB_C SAC3_GANP SANT_DAMP1_like SatD SelB-wing_1 SelB-wing_2 SelB-wing_3 SgrR_N Sigma54_CBD Sigma54_DBD Sigma70_ECF Sigma70_ner Sigma70_r2 Sigma70_r3 Sigma70_r4 Sigma70_r4_2 SLIDE SMC_ScpB SpoIIID STN1_2 Sulfolobus_pRN SWIRM TBPIP Terminase_5 TetR_N TFIIE_alpha TFIIE_beta TFIIF_alpha TFIIF_beta Tn7_Tnp_TnsA_C Tn916-Xis TraI_2_C Trans_reg_C TrfA TrmB Trp_repressor UPF0122 Vir_act_alpha_C YdaS_antitoxin YjcQ YokU z-alpha
We store a range of different sequence alignments for families. As well as the seed alignment from which the family is built, we provide the full alignment, generated by searching the sequence database (reference proteomes) using the family HMM. We also generate alignments using four representative proteomes (RP) sets, the UniProtKB sequence database, the NCBI sequence database, and our metagenomics sequence database. More...
There are various ways to view or download the sequence alignments that we store. We provide several sequence viewers and a plain-text Stockholm-format file for download.
We make a range of alignments for each Pfam-A family:
- the curated alignment from which the HMM for the family is built
- the alignment generated by searching the sequence database using the HMM
- Representative Proteomes (RPs) at 15%, 35%, 55% and 75% co-membership thresholds
- alignment generated by searching the UniProtKB sequence database using the family HMM
- alignment generated by searching the NCBI sequence database using the family HMM
- alignment generated by searching the metagenomics sequence database using the family HMM
You can see the alignments as HTML or in three different sequence viewers:
- a Java applet developed at the University of Dundee. You will need Java installed before running jalview
- an HTML page showing the whole alignment.Please note: full Pfam alignments can be very large. These HTML views are extremely large and often cause problems for browsers. Please use either jalview or the Pfam viewer if you have trouble viewing the HTML version
- an HTML-based representation of the alignment, coloured according to the posterior-probability (PP) values from the HMM. As for the standard HTML view, heatmap alignments can also be very large and slow to render.
You can download (or view in your browser) a text representation of a Pfam alignment in various formats:
You can also change the order in which sequences are listed in the alignment, change how insertions are represented, alter the characters that are used to represent gaps in sequences and, finally, choose whether to download the alignment or to view it in your browser directly.
You may find that large alignments cause problems for the viewers and the reformatting tool, so we also provide all alignments in Stockholm format. You can download either the plain text alignment, or a gzipped version of it.
We make a range of alignments for each Pfam-A family. You can see a description of each above. You can view these alignments in various ways but please note that some types of alignment are never generated while others may not be available for all families, most commonly because the alignments are too large to handle.
1Cannot generate PP/Heatmap alignments for seeds; no PP data available
Key: available, not generated, — not available.
Format an alignment
We make all of our alignments available in Stockholm format. You can download them here as raw, plain text files or as gzip-compressed files.
You can also download a FASTA format file containing the full-length sequences for all sequences in the full alignment.
HMM logos is one way of visualising profile HMMs. Logos provide a quick overview of the properties of an HMM in a graphical form. You can see a more detailed description of HMM logos and find out how you can interpret them here. More...
If you find these logos useful in your own work, please consider citing the following article:
This page displays the phylogenetic tree for this family's seed alignment. We use FastTree to calculate neighbour join trees with a local bootstrap based on 100 resamples (shown next to the tree nodes). FastTree calculates approximately-maximum-likelihood phylogenetic trees from our seed alignment.
Note: You can also download the data file for the tree.
Curation and family details
This section shows the detailed information about the Pfam family. You can see the definitions of many of the terms in this section in the glossary and a fuller explanation of the scoring system that we use in the scores section of the help pages.
|Number in seed:||40|
|Number in full:||1931|
|Average length of the domain:||68.40 aa|
|Average identity of full alignment:||55 %|
|Average coverage of the sequence by the domain:||16.88 %|
|HMM build commands:||
build method: hmmbuild -o /dev/null HMM SEED
search method: hmmsearch -Z 26740544 -E 1000 --cpu 4 HMM pfamseq
|Family (HMM) version:||16|
|Download:||download the raw HMM for this family|
Weight segments by...
Change the size of the sunburst
selected sequences to HMM
a FASTA-format file
- 0 sequences
- 0 species
This visualisation provides a simple graphical representation of the distribution of this family across species. You can find the original interactive tree in the More....
This chart is a modified "sunburst" visualisation of the species tree for this family. It shows each node in the tree as a separate arc, arranged radially with the superkingdoms at the centre and the species arrayed around the outermost ring.
How the sunburst is generated
The tree is built by considering the taxonomic lineage of each sequence that has a match to this family. For each node in the resulting tree, we draw an arc in the sunburst. The radius of the arc, its distance from the root node at the centre of the sunburst, shows the taxonomic level ("superkingdom", "kingdom", etc). The length of the arc represents either the number of sequences represented at a given level, or the number of species that are found beneath the node in the tree. The weighting scheme can be changed using the sunburst controls.
In order to reduce the complexity of the representation, we reduce the number of taxonomic levels that we show. We consider only the following eight major taxonomic levels:
Colouring and labels
Segments of the tree are coloured approximately according to their superkingdom. For example, archeal branches are coloured with shades of orange, eukaryotes in shades of purple, etc. The colour assignments are shown under the sunburst controls. Where space allows, the name of the taxonomic level will be written on the arc itself.
As you move your mouse across the sunburst, the current node will be highlighted. In the top section of the controls panel we show a summary of the lineage of the currently highlighed node. If you pause over an arc, a tooltip will be shown, giving the name of the taxonomic level in the title and a summary of the number of sequences and species below that node in the tree.
Anomalies in the taxonomy tree
There are some situations that the sunburst tree cannot easily handle and for which we have work-arounds in place.
Missing taxonomic levels
Some species in the taxonomic tree may not have one or more of the main eight levels that we display. For example, Bos taurus is not assigned an order in the NCBI taxonomic tree. In such cases we mark the omitted level with, for example, "No order", in both the tooltip and the lineage summary.
Unmapped species names
The tree is built by looking at each sequence in the full alignment for the family. We take the name of the species given by UniProt and try to map that to the full taxonomic tree from NCBI. In some cases, the name chosen by UniProt does not map to any node in the NCBI tree, perhaps because the chosen name is listed as a synonym or a misspelling in the NCBI taxonomy.
So that these nodes are not simply omitted from the sunburst tree, we group them together in a separate branch (or segment of the sunburst tree). Since we cannot determine the lineage for these unmapped species, we show all levels between the superkingdom and the species as "uncategorised".
Since we reduce the species tree to only the eight main taxonomic levels, sequences that are mapped to the sub-species level in the tree would not normally be shown. Rather than leave out these species, we map them instead to their parent species. So, for example, for sequences belonging to one of the Vibrio cholerae sub-species in the NCBI taxonomy, we show them instead as belonging to the species Vibrio cholerae.
Too many species/sequences
For large species trees, you may see blank regions in the outer layers of the sunburst. These occur when there are large numbers of arcs to be drawn in a small space. If an arc is less than approximately one pixel wide, it will not be drawn and the space will be left blank. You may still be able to get some information about the species in that region by moving your mouse across the area, but since each arc will be very small, it will be difficult to accurately locate a particular species.
The tree shows the occurrence of this domain across different species. More...
We show the species tree in one of two ways. For smaller trees we try to show an interactive representation, which allows you to select specific nodes in the tree and view them as an alignment or as a set of Pfam domain graphics.
Unfortunately we have found that there are problems viewing the interactive tree when the it becomes larger than a certain limit. Furthermore, we have found that Internet Explorer can become unresponsive when viewing some trees, regardless of their size. We therefore show a text representation of the species tree when the size is above a certain limit or if you are using Internet Explorer to view the site.
If you are using IE you can still load the interactive tree by clicking the "Generate interactive tree" button, but please be aware of the potential problems that the interactive species tree can cause.
For all of the domain matches in a full alignment, we count the number that are found on all sequences in the alignment. This total is shown in the purple box.
We also count the number of unique sequences on which each domain is found, which is shown in green. Note that a domain may appear multiple times on the same sequence, leading to the difference between these two numbers.
Finally, we group sequences from the same organism according to the NCBI code that is assigned by UniProt, allowing us to count the number of distinct sequences on which the domain is found. This value is shown in the pink boxes.
We use the NCBI species tree to group organisms according to their taxonomy and this forms the structure of the displayed tree. Note that in some cases the trees are too large (have too many nodes) to allow us to build an interactive tree, but in most cases you can still view the tree in a plain text, non-interactive representation. Those species which are represented in the seed alignment for this domain are highlighted.
You can use the tree controls to manipulate how the interactive tree is displayed:
- show/hide the summary boxes
- highlight species that are represented in the seed alignment
- expand/collapse the tree or expand it to a given depth
- select a sub-tree or a set of species within the tree and view them graphically or as an alignment
- save a plain text representation of the tree
Please note: for large trees this can take some time. While the tree is loading, you can safely switch away from this tab but if you browse away from the family page entirely, the tree will not be loaded.
There are 5 interactions for this family. More...
We determine these interactions using iPfam, which considers the interactions between residues in three-dimensional protein structures and maps those interactions back to Pfam families. You can find more information about the iPfam algorithm in the journal article that accompanies the website.
For those sequences which have a structure in the Protein DataBank, we use the mapping between UniProt, PDB and Pfam coordinate systems from the PDBe group, to allow us to map Pfam domains onto UniProt sequences and three-dimensional protein structures. The table below shows the structures on which the Pou domain has been found. There are 22 instances of this domain found in the PDB. Note that there may be multiple copies of the domain in a single PDB structure, since many structures contain multiple copies of the same protein seqence.
Loading structure mapping...