Summary: ADP-ribosylation factor family
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 "ADP ribosylation factor". 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.
ADP ribosylation factor Edit Wikipedia article
ADP Ribosylation Factors (ARFs) are members of the ARF family of GTP-binding proteins of the Ras superfamily. ARF family proteins are ubiquitous in eukaryotic cells, and six highly conserved members of the family have been identified in mammalian cells. Although ARFs are soluble, they generally associate with membranes because of N-terminus myristoylation. They function as regulators of vesicular traffic and actin remodelling.
The small ADP ribosylation factor (Arf) GTP-binding proteins are major regulators of vesicle biogenesis in intracellular traffic. They are the founding members of a growing family that includes Arl (Arf-like), Arp (Arf-related proteins) and the remotely related Sar (Secretion-associated and Ras-related) proteins. Arf proteins cycle between inactive GDP-bound and active GTP-bound forms that bind selectively to effectors. The classical structural GDP/GTP switch is characterised by conformational changes at the so-called switch 1 and switch 2 regions, which bind tightly to the gamma-phosphate of GTP but poorly or not at all to the GDP nucleotide. Structural studies of Arf1 and Arf6 have revealed that although these proteins feature the switch 1 and 2 conformational changes, they depart from other small GTP-binding proteins in that they use an additional, unique switch to propagate structural information from one side of the protein to the other.
The GDP/GTP structural cycles of human Arf1 and Arf6 feature a unique conformational change that affects the beta2beta3 strands connecting switch 1 and switch 2 (interswitch) and also the amphipathic helical N-terminus. In GDP-bound Arf1 and Arf6, the interswitch is retracted and forms a pocket to which the N-terminal helix binds, the latter serving as a molecular hasp to maintain the inactive conformation. In the GTP-bound form of these proteins, the interswitch undergoes a two-residue register shift that pulls switch 1 and switch 2 up, restoring an active conformation that can bind GTP. In this conformation, the interswitch projects out of the protein and extrudes the N-terminal hasp by occluding its binding pocket.
ARFs regularly associate with two types of protein, those involved in catalyzing GTP/GDP exchange, and those that serve other functions.
GTP/GDP exchange proteins
ARF binds to two forms of the guanosine nucleotide, guanosine triphosphate (GTP) and guanosine diphosphate (GDP). The shape of the ARF molecule is dependent upon the form to which it is bound, allowing it to serve in a regulatory capacity. ARF requires assistance from other proteins in order to switch between binding to GTP and GDP. GTPase activating proteins (GAPs) force ARF to hydrolyze bound GTP to GDP, and Guanine nucleotide exchange factors force ARF to adopt a new GTP molecule in place of a bound GDP.
Other proteins interact with ARF, depending upon whether or not it is bound to GTP or GDP. The active form, ARF*GTP, binds to vesicle coat proteins and adaptors, including coat protein I (COPI) and various phospholipids. The inactive form is only known to bind to a class of transmembrane proteins. Different types of ARF bind specifically different kinds of effector proteins.
There are currently 6 known mammalian ARF proteins, which are divided into three classes of ARFs:
ARFs are small proteins of approximately 20 kD in size. They contain two switch regions, which change relative positions between cycles of GDP/GTP-binding. ARFs are frequently myristoylated in their N-terminal region, which contributes to their membrane association.
Human genes encoding proteins containing this domain include:
- ARF1 ARF3 ARF4 ARF5 ARF6 ARFRP1
- ARL1 ARL2 ARL2L1 ARL3 ARL4A ARL4C ARL4D ARL5 ARL5A ARL5B
- ARL10 ARL11 ARL13A ARL13B ARL14 ARL15 ARL16 ARL17
- ARL6 ARL7 ARL8A ARL8B ARL9
- SAR1A SAR1B SAR1P3 SARA1 TRIM23
- Donaldson JG, Honda A (2005). "Localization and function of Arf family GTPases". Biochemical Society Transactions 33 (4): 639–642. doi:10.1042/BST0330639. PMID 16042562.
- Nie Z, Hirsch DS, Randazzo PA (2003). "Arf and its many interactors". Current opinion in cell biology 15 (4): 396–404. doi:10.1016/S0955-0674(03)00071-1. PMID 12892779.
- Amor JC, Harrison DH, Kahn RA, Ringe D (1994). "Structure of the human ADP-ribosylation factor 1 complexed with GDP". Nature 372 (6507): 704–708. doi:10.1038/372704a0. PMID 7990966.
- Moss J, Vaughan M; Vaughan (1995). "Structure and function of ARF proteins: Activators of cholera toxin and critical components of intracellular vesicular transport processes". The Journal of Biological Chemistry 270 (21): 12327–12330. doi:10.1074/jbc.270.21.12327. PMID 7759471.
- Boman AL, Kahn RA; Kahn (1995). "Arf proteins: The membrane traffic police?". Trends in Biochemical Sciences 20 (4): 147–150. doi:10.1016/s0968-0004(00)88991-4. PMID 7770914.
- Kahn RA, Kern FG, Clark J, Gelmann EP, Rulka C (1991). "Human ADP-ribosylation factors. A functionally conserved family of GTP-binding proteins". The Journal of Biological Chemistry 266 (4): 2606–2614. PMID 1899243.
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.
ADP-ribosylation factor family Provide feedback
Pfam combines a number of different Prosite families together
Moss J, Vaughan M; , J. Biol. Chem. 1995;270:12327-12330.: Structure and function of ARF proteins: Activators of cholera toxin and critical components of intracellular vesicular transport processes. PUBMED:7759471 EPMC:7759471
Internal database links
|SCOOP:||Ras G-alpha MMR_HSR1 MCR_beta FeoB_N Gtr1_RagA NOG1 Roc SRPRB CENP-M DUF3142 MnmE_helical DUF3963 MMR_HSR1_Xtn|
|Similarity to PfamA using HHSearch:||AAA GTP_EFTU Ras G-alpha G-alpha MMR_HSR1 FeoB_N cobW ATP_bind_1 ArgK Gtr1_RagA Roc SRPRB PduV-EutP MnmE_helical AAA_22|
External database links
|PROSITE:||PDOC00781 PDOC00017 PDOC01020|
This tab holds annotation information from the InterPro database.
InterPro entry IPR006689
Small GTPases form an independent superfamily within the larger class of regulatory GTP hydrolases. This superfamily contains proteins that control a vast number of important processes and possess a common, structurally preserved GTP-binding domain [PUBMED:2122258, PUBMED:1898771]. Sequence comparisons of small G proteins from various species have revealed that they are conserved in primary structures at the level of 30-55% similarity [PUBMED:2029511].
Crystallographic analysis of various small G proteins revealed the presence of a 20 kDa catalytic domain that is unique for the whole superfamily [PUBMED:1898771, PUBMED:2196171]. The domain is built of five alpha helices (A1-A5), six beta-strands (B1-B6) and five polypeptide loops (G1-G5). A structural comparison of the GTP- and GDP-bound form, allows one to distinguish two functional loop regions: switch I and switch II that surround the gamma-phosphate group of the nucleotide. The G1 loop (also called the P-loop) that connects the B1 strand and the A1 helix is responsible for the binding of the phosphate groups. The G3 loop provides residues for Mg(2+) and phosphate binding and is located at the N terminus of the A2 helix. The G1 and G3 loops are sequentially similar to Walker A and Walker B boxes that are found in other nucleotide binding motifs. The G2 loop connects the A1 helix and the B2 strand and contains a conserved Thr residue responsible for Mg(2+) binding. The guanine base is recognised by the G4 and G5 loops. The consensus sequence NKXD of the G4 loop contains Lys and Asp residues directly interacting with the nucleotide. Part of the G5 loop located between B6 and A5 acts as a recognition site for the guanine base [PUBMED:11995995].
The small GTPase superfamily can be divided into at least 8 different families, including:
- Arf small GTPases. GTP-binding proteins involved in protein trafficking by modulating vesicle budding and uncoating within the Golgi apparatus.
- Ran small GTPases. GTP-binding proteins involved in nucleocytoplasmic transport. Required for the import of proteins into the nucleus and also for RNA export.
- Rab small GTPases. GTP-binding proteins involved in vesicular traffic.
- Rho small GTPases. GTP-binding proteins that control cytoskeleton reorganisation.
- Ras small GTPases. GTP-binding proteins involved in signalling pathways.
- Sar1 small GTPases. Small GTPase component of the coat protein complex II (COPII) which promotes the formation of transport vesicles from the endoplasmic reticulum (ER).
- Mitochondrial Rho (Miro). Small GTPase domain found in mitochondrial proteins involved in mitochondrial trafficking.
- Roc small GTPases domain. Small GTPase domain always found associated with the COR domain.
This entry represents a branch of the small GTPase superfamily that includes the ADP ribosylation factor Arf, Arl (Arf-like), Arp (Arf-related proteins) and the remotely related Sar (Secretion-associated and Ras-related) proteins. Arf proteins are major regulators of vesicle biogenesis in intracellular traffic [PUBMED:12429613]. They cycle between inactive GDP-bound and active GTP-bound forms that bind selectively to effectors. The classical structural GDP/GTP switch is characterised by conformational changes at the so-called switch 1 and switch 2 regions, which bind tightly to the gamma-phosphate of GTP but poorly or not at all to the GDP nucleotide. Structural studies of Arf1 and Arf6 have revealed that although these proteins feature the switch 1 and 2 conformational changes, they depart from other small GTP-binding proteins in that they use an additional, unique switch to propagate structural information from one side of the protein to the other.
The GDP/GTP structural cycles of human Arf1 and Arf6 feature a unique conformational change that affects the beta2-beta3 strands connecting switch 1 and switch 2 (interswitch) and also the amphipathic helical N terminus. In GDP-bound Arf1 and Arf6, the interswitch is retracted and forms a pocket to which the N-terminal helix binds, the latter serving as a molecular hasp to maintain the inactive conformation. In the GTP-bound form of these proteins, the interswitch undergoes a two-residue register shift that pulls switch 1 and switch 2 up, restoring an active conformation that can bind GTP. In this conformation, the interswitch projects out of the protein and extrudes the N-terminal hasp by occluding its binding pocket.
The mapping between Pfam and Gene Ontology is provided by InterPro. If you use this data please cite InterPro.
|Molecular function||GTP binding (GO:0005525)|
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...
AAA family proteins often perform chaperone-like functions that assist in the assembly, operation, or disassembly of protein complexes .
The clan contains the following 199 members:6PF2K AAA AAA-ATPase_like AAA_10 AAA_11 AAA_12 AAA_13 AAA_14 AAA_15 AAA_16 AAA_17 AAA_18 AAA_19 AAA_2 AAA_21 AAA_22 AAA_23 AAA_24 AAA_25 AAA_26 AAA_27 AAA_28 AAA_29 AAA_3 AAA_30 AAA_31 AAA_32 AAA_33 AAA_34 AAA_35 AAA_5 AAA_6 AAA_7 AAA_8 AAA_PrkA ABC_ATPase ABC_tran Adeno_IVa2 Adenylsucc_synt ADK AFG1_ATPase AIG1 APS_kinase Arf ArgK ArsA_ATPase ATP-synt_ab ATP_bind_1 ATP_bind_2 ATPase ATPase_2 Bac_DnaA CbiA CBP_BcsQ CDC73_C CLP1_P CMS1 CoaE CobA_CobO_BtuR CobU cobW CPT CTP_synth_N Cytidylate_kin Cytidylate_kin2 DAP3 DEAD DEAD_2 DLIC DNA_pack_C DNA_pack_N DNA_pol3_delta DNA_pol3_delta2 DnaB_C dNK DUF1611 DUF2075 DUF2326 DUF2478 DUF258 DUF2791 DUF2813 DUF3584 DUF463 DUF815 DUF853 DUF87 DUF927 Dynamin_N ERCC3_RAD25_C Exonuc_V_gamma FeoB_N Fer4_NifH Flavi_DEAD FTHFS FtsK_SpoIIIE G-alpha Gal-3-0_sulfotr GBP GTP_EFTU Gtr1_RagA Guanylate_kin GvpD HDA2-3 Helicase_C Helicase_C_2 Helicase_C_4 Helicase_RecD Herpes_Helicase Herpes_ori_bp Herpes_TK Hydin_ADK IIGP IPPT IPT IstB_IS21 KAP_NTPase KdpD Kinesin KTI12 Lon_2 LpxK MCM MEDS Mg_chelatase Microtub_bd MipZ MMR_HSR1 MobB MukB MutS_V Myosin_head NACHT NB-ARC NOG1 NTPase_1 NTPase_P4 ParA Parvo_NS1 PAXNEB PduV-EutP PhoH PIF1 Podovirus_Gp16 Polyoma_lg_T_C Pox_A32 PPK2 PPV_E1_C PRK Rad17 Rad51 Ras RecA ResIII RHD3 RHSP RNA12 RNA_helicase Roc RuvB_N SbcCD_C SecA_DEAD Septin Sigma54_activ_2 Sigma54_activat SKI SMC_N SNF2_N Spore_IV_A SRP54 SRPRB SulA Sulfotransfer_1 Sulfotransfer_2 Sulfotransfer_3 Sulphotransf T2SSE T4SS-DNA_transf Terminase_1 Terminase_3 Terminase_6 Terminase_GpA Thymidylate_kin TIP49 TK TniB Torsin TraG-D_C tRNA_lig_kinase TrwB_AAD_bind TsaE UvrD-helicase UvrD_C UvrD_C_2 Viral_helicase1 VirC1 VirE Zeta_toxin Zot
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:||20|
|Number in full:||8708|
|Average length of the domain:||161.00 aa|
|Average identity of full alignment:||36 %|
|Average coverage of the sequence by the domain:||77.19 %|
|HMM build commands:||
build method: hmmbuild -o /dev/null HMM SEED
search method: hmmsearch -Z 17690987 -E 1000 --cpu 4 HMM pfamseq
|Family (HMM) version:||19|
|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 22 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 Arf domain has been found. There are 180 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...