Summary: PCI domain
Pfam includes annotations and additional family information from a range of different sources. These sources can be accessed via the tabs below.
The Pfam group coordinates the annotation of Pfam families in Wikipedia, but we have not yet assigned a Wikipedia article to this family. If you think that a particular Wikipedia article provides good annotation, please let us know.
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.
PCI domain Provide feedback
This domain has also been called the PINT motif (Proteasome, Int-6, Nip-1 and TRIP-15) .
Sha Z, Yen HC, Scheel H, Suo J, Hofmann K, Chang EC; , J Biol Chem. 2007; [Epub ahead of print]: Isolation of the Schizosaccharomyces pombe proteasome subunit Rpn7 and a structure-function study of the PCI domain. PUBMED:17761670 EPMC:17761670
Internal database links
|Similarity to PfamA using HHSearch:||DDRGK CSN8_PSD8_EIF3K|
This tab holds annotation information from the InterPro database.
InterPro entry IPR000717
The PCI (for Proteasome, COP9, Initiation factor 3) domain (sometimes also referred to as the PINT domain, for Proteasome subunits, Int-6, Nip-1, and Trip-15) is present in six different subunits of 26 proteasome lid, COP9 signalosome (CSN) and eukaryotic translation initiation factor-3 (eIF3) complexes, as well as in subunits of certain other multiprotein complexes. The PCI domain mediates and stabilizes protein-protein interactions within the complexes. The role of the PCI domains is most likely that of a scaffold for the other complex subunits and other binding partners. The PCI domain could play a role as a universal binding domain supporting intra-complex interactions as well as recruitments of additional ligands [ PUBMED:9644972 , PUBMED:9605331 , PUBMED:15790418 , PUBMED:23818606 , PUBMED:15180986 , PUBMED:18854373 ].
PCI is an ~190-amino acid domain, not well conserved in its primary sequence, usually located near the C terminus of the protein. It does not contain any invariant residues or any conserved pattern of charged residues that would suggest a catalytic activity. The PCI domain is comprised of two subdomains that are intimately connected, an N-terminal helical bundle (HB) subdomain and a C-terminal globular winged helix (WH) subdomain. The C- terminal half of the PCI domain is much better conserved than the N-terminal half [ PUBMED:23818606 , PUBMED:15180986 , PUBMED:18854373 ].
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 381 members:AbiEi_3_N AbiEi_4 ANAPC2 AphA_like AraR_C Arg_repressor ARID ArsR B-block_TFIIIC B5 Bac_DnaA_C Baculo_PEP_N BetR BHD_3 BLACT_WH Bot1p BrkDBD BrxA BsuBI_PstI_RE_N C_LFY_FLO CaiF_GrlA CarD_CdnL_TRCF CDC27 Cdc6_C Cdh1_DBD_1 CDT1 CDT1_C CENP-B_N Costars CPSase_L_D3 Cro Crp CSN4_RPN5_eIF3a CSN8_PSD8_EIF3K CtsR Cullin_Nedd8 CUT CUTL CvfB_WH DBD_HTH DDRGK DEP Dimerisation Dimerisation2 DNA_binding_1 DNA_meth_N DpnI_C DprA_WH DsrC DsrD DUF1016_N DUF1133 DUF1153 DUF1323 DUF134 DUF1376 DUF1441 DUF1492 DUF1495 DUF1670 DUF1804 DUF1836 DUF1870 DUF2089 DUF2250 DUF2316 DUF2513 DUF2551 DUF2582 DUF3116 DUF3161 DUF3253 DUF3489 DUF3853 DUF3860 DUF3895 DUF3908 DUF433 DUF434 DUF4364 DUF4373 DUF4423 DUF4447 DUF4777 DUF480 DUF4817 DUF5635 DUF573 DUF5805 DUF6088 DUF6262 DUF6362 DUF6432 DUF6462 DUF6471 DUF722 DUF739 DUF742 DUF937 DUF977 E2F_TDP EAP30 eIF-5_eIF-2B ELL ESCRT-II Ets EutK_C Exc F-112 FaeA Fe_dep_repr_C Fe_dep_repress FeoC FokI_D1 FokI_dom_2 Forkhead FtsK_gamma FUR GcrA GerE GntR GP3_package HARE-HTH HemN_C HNF-1_N Homeobox_KN Homeodomain 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_48 HTH_49 HTH_5 HTH_50 HTH_51 HTH_52 HTH_53 HTH_54 HTH_55 HTH_56 HTH_57 HTH_58 HTH_59 HTH_6 HTH_60 HTH_61 HTH_7 HTH_8 HTH_9 HTH_ABP1_N HTH_AraC HTH_AsnC-type HTH_CodY HTH_Crp_2 HTH_DeoR HTH_IclR HTH_Mga HTH_micro HTH_OrfB_IS605 HTH_PafC HTH_ParB HTH_psq HTH_SUN2 HTH_Tnp_1 HTH_Tnp_1_2 HTH_Tnp_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 KilA-N Kin17_mid KORA KorB La LacI LexA_DNA_bind Linker_histone LZ_Tnp_IS481 MADF_DNA_bdg MAGE MARF1_LOTUS MarR MarR_2 MC6 MC7 MC8 MerR MerR-DNA-bind MerR_1 MerR_2 Mga Mnd1 MogR_DNAbind Mor MotA_activ MqsA_antitoxin MRP-L20 Mrr_N MukE 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 NFRKB_winged NOD2_WH NUMOD1 ORC_WH_C OST-HTH P22_Cro PaaX PadR PapB PAX PCI Penicillinase_R Phage_AlpA Phage_antitermQ Phage_CI_repr Phage_CII Phage_NinH Phage_Nu1 Phage_rep_O Phage_rep_org_N Phage_terminase PheRS_DBD1 PheRS_DBD2 PheRS_DBD3 PhetRS_B1 Pou Pox_D5 PqqD PRC2_HTH_1 PUFD PuR_N Put_DNA-bind_N pXO2-72 Raf1_HTH Rap1-DNA-bind Rep_3 RepA_C RepA_N RepB RepC RepL Replic_Relax RFX_DNA_binding Ribosomal_S18 Ribosomal_S19e Ribosomal_S25 Rio2_N RNA_pol_Rpc34 RNA_pol_Rpc82 RNase_H2-Ydr279 ROQ_II ROXA-like_wH RP-C RPA RPA_C RPN6_C_helix RQC Rrf2 RTP RuvB_C S10_plectin 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 SinI SKA1 Ski_Sno SLIDE Slx4 SMC_Nse1 SMC_ScpB SoPB_HTH SpoIIID SRP19 SRP_SPB STN1_2 Stn1_C Stork_head Sulfolobus_pRN Suv3_N Swi6_N SWIRM Tau95 TBPIP TEA Terminase_5 TetR_N TFA2_Winged_2 TFIIE_alpha TFIIE_beta TFIIF_alpha TFIIF_beta Tn7_Tnp_TnsA_C Tn916-Xis TraI_2_C Trans_reg_C TrfA TrmB tRNA_bind_2 tRNA_bind_3 Trp_repressor UPF0122 UPF0175 Vir_act_alpha_C XPA_C Xre-like-HTH YdaS_antitoxin YidB 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 and the UniProtKB 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
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:||70|
|Number in full:||26356|
|Average length of the domain:||109.6 aa|
|Average identity of full alignment:||17 %|
|Average coverage of the sequence by the domain:||21.5 %|
|HMM build commands:||
build method: hmmbuild -o /dev/null HMM SEED
search method: hmmsearch -Z 61295632 -E 1000 --cpu 4 HMM pfamseq
|Family (HMM) version:||30|
|Download:||download the raw HMM for this family|
Weight segments by...
Change the size of the sunburst
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.
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 PCI domain has been found. There are 453 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 sequence.
Loading structure mapping...
AlphaFold Structure Predictions
The list of proteins below match this family and have AlphaFold predicted structures. Click on the protein accession to view the predicted structure.