Английская Википедия:Folding@home

Материал из Онлайн справочника
Перейти к навигацииПерейти к поиску

Шаблон:Short description Шаблон:Use American English Шаблон:Infobox software

Folding@home (FAH or F@h) is a distributed computing project aimed to help scientists develop new therapeutics for a variety of diseases by the means of simulating protein dynamics. This includes the process of protein folding and the movements of proteins, and is reliant on simulations run on volunteers' personal computers.[1] Folding@home is currently based at the University of Pennsylvania and led by Greg Bowman, a former student of Vijay Pande.[2]

The project utilizes graphics processing units (GPUs), central processing units (CPUs), and ARM processors like those on the Raspberry Pi for distributed computing and scientific research. The project uses statistical simulation methodology that is a paradigm shift from traditional computing methods.[3] As part of the client–server model network architecture, the volunteered machines each receive pieces of a simulation (work units), complete them, and return them to the project's database servers, where the units are compiled into an overall simulation. Volunteers can track their contributions on the Folding@home website, which makes volunteers' participation competitive and encourages long-term involvement.

Folding@home is one of the world's fastest computing systems. With heightened interest in the project as a result of the COVID-19 pandemic,[4] the system achieved a speed of approximately 1.22 exaflops by late March 2020 and reached 2.43 exaflops by April 12, 2020,[5] making it the world's first exaflop computing system. This level of performance from its large-scale computing network has allowed researchers to run computationally costly atomic-level simulations of protein folding thousands of times longer than formerly achieved. Since its launch on October 1, 2000, Folding@home was involved in the production of 226 scientific research papers.[6] Results from the project's simulations agree well with experiments.[7][8][9]

Background

Шаблон:Further

Файл:Protein folding.png
A protein before and after folding. It starts in an unstable random coil state and finishes in its native state conformation.

Proteins are an essential component to many biological functions and participate in virtually all processes within biological cells. They often act as enzymes, performing biochemical reactions including cell signaling, molecular transportation, and cellular regulation. As structural elements, some proteins act as a type of skeleton for cells, and as antibodies, while other proteins participate in the immune system. Before a protein can take on these roles, it must fold into a functional three-dimensional structure, a process that often occurs spontaneously and is dependent on interactions within its amino acid sequence and interactions of the amino acids with their surroundings. Protein folding is driven by the search to find the most energetically favorable conformation of the protein, i.e., its native state. Thus, understanding protein folding is critical to understanding what a protein does and how it works, and is considered a holy grail of computational biology.[10][11] Despite folding occurring within a crowded cellular environment, it typically proceeds smoothly. However, due to a protein's chemical properties or other factors, proteins may misfold, that is, fold down the wrong pathway and end up misshapen. Unless cellular mechanisms can destroy or refold misfolded proteins, they can subsequently aggregate and cause a variety of debilitating diseases.[12] Laboratory experiments studying these processes can be limited in scope and atomic detail, leading scientists to use physics-based computing models that, when complementing experiments, seek to provide a more complete picture of protein folding, misfolding, and aggregation.[13][14]

Due to the complexity of proteins' conformation or configuration space (the set of possible shapes a protein can take), and limits in computing power, all-atom molecular dynamics simulations have been severely limited in the timescales that they can study. While most proteins typically fold in the order of milliseconds,[13][15] before 2010, simulations could only reach nanosecond to microsecond timescales.[7] General-purpose supercomputers have been used to simulate protein folding, but such systems are intrinsically costly and typically shared among many research groups. Further, because the computations in kinetic models occur serially, strong scaling of traditional molecular simulations to these architectures is exceptionally difficult.[16][17] Moreover, as protein folding is a stochastic process (i.e., random) and can statistically vary over time, it is challenging computationally to use long simulations for comprehensive views of the folding process.[18][19]

Файл:ACBP MSM from Folding@home.tiff
Folding@home uses Markov state models, like the one diagrammed here, to model the possible shapes and folding pathways a protein can take as it condenses from its initial randomly coiled state (left) into its native 3-D structure (right).

Protein folding does not occur in one step.[12] Instead, proteins spend most of their folding time, nearly 96% in some cases,[20] waiting in various intermediate conformational states, each a local thermodynamic free energy minimum in the protein's energy landscape. Through a process known as adaptive sampling, these conformations are used by Folding@home as starting points for a set of simulation trajectories. As the simulations discover more conformations, the trajectories are restarted from them, and a Markov state model (MSM) is gradually created from this cyclic process. MSMs are discrete-time master equation models which describe a biomolecule's conformational and energy landscape as a set of distinct structures and the short transitions between them. The adaptive sampling Markov state model method significantly increases the efficiency of simulation as it avoids computation inside the local energy minimum itself, and is amenable to distributed computing (including on GPUGRID) as it allows for the statistical aggregation of short, independent simulation trajectories.[21] The amount of time it takes to construct a Markov state model is inversely proportional to the number of parallel simulations run, i.e., the number of processors available. In other words, it achieves linear parallelization, leading to an approximately four orders of magnitude reduction in overall serial calculation time. A completed MSM may contain tens of thousands of sample states from the protein's phase space (all the conformations a protein can take on) and the transitions between them. The model illustrates folding events and pathways (i.e., routes) and researchers can later use kinetic clustering to view a coarse-grained representation of the otherwise highly detailed model. They can use these MSMs to reveal how proteins misfold and to quantitatively compare simulations with experiments.[3][18][22]

Between 2000 and 2010, the length of the proteins Folding@home has studied have increased by a factor of four, while its timescales for protein folding simulations have increased by six orders of magnitude.[23] In 2002, Folding@home used Markov state models to complete approximately a million CPU days of simulations over the span of several months,[9] and in 2011, MSMs parallelized another simulation that required an aggregate 10 million CPU hours of computing.[24] In January 2010, Folding@home used MSMs to simulate the dynamics of the slow-folding 32-residue NTL9 protein out to 1.52 milliseconds, a timescale consistent with experimental folding rate predictions but a thousand times longer than formerly achieved. The model consisted of many individual trajectories, each two orders of magnitude shorter, and provided an unprecedented level of detail into the protein's energy landscape.[3][7][25] In 2010, Folding@home researcher Gregory Bowman was awarded the Thomas Kuhn Paradigm Shift Award from the American Chemical Society for the development of the open-source MSMBuilder software and for attaining quantitative agreement between theory and experiment.[26][27] For his work, Pande was awarded the 2012 Michael and Kate Bárány Award for Young Investigators for "developing field-defining and field-changing computational methods to produce leading theoretical models for protein and RNA folding",[28] and the 2006 Irving Sigal Young Investigator Award for his simulation results which "have stimulated a re-examination of the meaning of both ensemble and single-molecule measurements, making Pande's efforts pioneering contributions to simulation methodology."[29]

Examples of application in biomedical research

Protein misfolding can result in a variety of diseases including Alzheimer's disease, cancer, Creutzfeldt–Jakob disease, cystic fibrosis, Huntington's disease, sickle-cell anemia, and type II diabetes.[12][30][31] Cellular infection by viruses such as HIV and influenza also involve folding events on cell membranes.[32] Once protein misfolding is better understood, therapies can be developed that augment cells' natural ability to regulate protein folding. Such therapies include the use of engineered molecules to alter the production of a given protein, help destroy a misfolded protein, or assist in the folding process.[33] The combination of computational molecular modeling and experimental analysis has the possibility to fundamentally shape the future of molecular medicine and the rational design of therapeutics,[14] such as expediting and lowering the costs of drug discovery.[34] The goal of the first five years of Folding@home was to make advances in understanding folding, while the current goal is to understand misfolding and related disease, especially Alzheimer's.[35]

The simulations run on Folding@home are used in conjunction with laboratory experiments,[18] but researchers can use them to study how folding in vitro differs from folding in native cellular environments. This is advantageous in studying aspects of folding, misfolding, and their relationships to disease that are difficult to observe experimentally. For example, in 2011, Folding@home simulated protein folding inside a ribosomal exit tunnel, to help scientists better understand how natural confinement and crowding might influence the folding process.[36][37] Furthermore, scientists typically employ chemical denaturants to unfold proteins from their stable native state. It is not generally known how the denaturant affects the protein's refolding, and it is difficult to experimentally determine if these denatured states contain residual structures which may influence folding behavior. In 2010, Folding@home used GPUs to simulate the unfolded states of Protein L, and predicted its collapse rate in strong agreement with experimental results.[38]

The large data sets from the project are freely available for other researchers to use upon request and some can be accessed from the Folding@home website.[39][40] The Pande lab has collaborated with other molecular dynamics systems such as the Blue Gene supercomputer,[41] and they share Folding@home's key software with other researchers, so that the algorithms which benefited Folding@home may aid other scientific areas.[39] In 2011, they released the open-source Copernicus software, which is based on Folding@home's MSM and other parallelizing methods and aims to improve the efficiency and scaling of molecular simulations on large computer clusters or supercomputers.[42][43] Summaries of all scientific findings from Folding@home are posted on the Folding@home website after publication.[44]

Alzheimer's disease

Шаблон:Multiple image

Alzheimer's disease is an incurable neurodegenerative disease which most often affects the elderly and accounts for more than half of all cases of dementia. Its exact cause remains unknown, but the disease is identified as a protein misfolding disease. Alzheimer's is associated with toxic aggregations of the amyloid beta (Aβ) peptide, caused by Aβ misfolding and clumping together with other Aβ peptides. These Aβ aggregates then grow into significantly larger senile plaques, a pathological marker of Alzheimer's disease.[45][46][47] Due to the heterogeneous nature of these aggregates, experimental methods such as X-ray crystallography and nuclear magnetic resonance (NMR) have had difficulty characterizing their structures. Moreover, atomic simulations of Aβ aggregation are highly demanding computationally due to their size and complexity.[48][49]

Preventing Aβ aggregation is a promising method to developing therapeutic drugs for Alzheimer's disease, according to Naeem and Fazili in a literature review article.[50] In 2008, Folding@home simulated the dynamics of Aβ aggregation in atomic detail over timescales of the order of tens of seconds. Prior studies were only able to simulate about 10 microseconds. Folding@home was able to simulate Aβ folding for six orders of magnitude longer than formerly possible. Researchers used the results of this study to identify a beta hairpin that was a major source of molecular interactions within the structure.[51] The study helped prepare the Pande lab for future aggregation studies and for further research to find a small peptide which may stabilize the aggregation process.[48]

In December 2008, Folding@home found several small drug candidates which appear to inhibit the toxicity of Aβ aggregates.[52] In 2010, in close cooperation with the Center for Protein Folding Machinery, these drug leads began to be tested on biological tissue.[31] In 2011, Folding@home completed simulations of several mutations of Aβ that appear to stabilize the aggregate formation, which could aid in the development of therapeutic drug therapies for the disease and greatly assist with experimental nuclear magnetic resonance spectroscopy studies of Aβ oligomers.[49][53] Later that year, Folding@home began simulations of various Aβ fragments to determine how various natural enzymes affect the structure and folding of Aβ.[54][55]

Huntington's disease

Huntington's disease is a neurodegenerative genetic disorder that is associated with protein misfolding and aggregation. Excessive repeats of the glutamine amino acid at the N-terminus of the huntingtin protein cause aggregation, and although the behavior of the repeats is not completely understood, it does lead to the cognitive decline associated with the disease.[56] As with other aggregates, there is difficulty in experimentally determining its structure.[57] Scientists are using Folding@home to study the structure of the huntingtin protein aggregate and to predict how it forms, assisting with rational drug design methods to stop the aggregate formation.[31] The N17 fragment of the huntingtin protein accelerates this aggregation, and while there have been several mechanisms proposed, its exact role in this process remains largely unknown.[58] Folding@home has simulated this and other fragments to clarify their roles in the disease.[59] Since 2008, its drug design methods for Alzheimer's disease have been applied to Huntington's.[31]

Cancer

More than half of all known cancers involve mutations of p53, a tumor suppressor protein present in every cell which regulates the cell cycle and signals for cell death in the event of damage to DNA. Specific mutations in p53 can disrupt these functions, allowing an abnormal cell to continue growing unchecked, resulting in the development of tumors. Analysis of these mutations helps explain the root causes of p53-related cancers.[60] In 2004, Folding@home was used to perform the first molecular dynamics study of the refolding of p53's protein dimer in an all-atom simulation of water. The simulation's results agreed with experimental observations and gave insights into the refolding of the dimer that were formerly unobtainable.[61] This was the first peer reviewed publication on cancer from a distributed computing project.[62] The following year, Folding@home powered a new method to identify the amino acids crucial for the stability of a given protein, which was then used to study mutations of p53. The method was reasonably successful in identifying cancer-promoting mutations and determined the effects of specific mutations which could not otherwise be measured experimentally.[63]

Folding@home is also used to study protein chaperones,[31] heat shock proteins which play essential roles in cell survival by assisting with the folding of other proteins in the crowded and chemically stressful environment within a cell. Rapidly growing cancer cells rely on specific chaperones, and some chaperones play key roles in chemotherapy resistance. Inhibitions to these specific chaperones are seen as potential modes of action for efficient chemotherapy drugs or for reducing the spread of cancer.[64] Using Folding@home and working closely with the Center for Protein Folding Machinery, the Pande lab hopes to find a drug which inhibits those chaperones involved in cancerous cells.[65] Researchers are also using Folding@home to study other molecules related to cancer, such as the enzyme Src kinase, and some forms of the engrailed homeodomain: a large protein which may be involved in many diseases, including cancer.[66][67] In 2011, Folding@home began simulations of the dynamics of the small knottin protein EETI, which can identify carcinomas in imaging scans by binding to surface receptors of cancer cells.[68][69]

Interleukin 2 (IL-2) is a protein that helps T cells of the immune system attack pathogens and tumors. However, its use as a cancer treatment is restricted due to serious side effects such as pulmonary edema. IL-2 binds to these pulmonary cells differently than it does to T cells, so IL-2 research involves understanding the differences between these binding mechanisms. In 2012, Folding@home assisted with the discovery of a mutant form of IL-2 which is three hundred times more effective in its immune system role but carries fewer side effects. In experiments, this altered form significantly outperformed natural IL-2 in impeding tumor growth. Pharmaceutical companies have expressed interest in the mutant molecule, and the National Institutes of Health are testing it against a large variety of tumor models to try to accelerate its development as a therapeutic.[70][71]

Osteogenesis imperfecta

Osteogenesis imperfecta, known as brittle bone disease, is an incurable genetic bone disorder which can be lethal. Those with the disease are unable to make functional connective bone tissue. This is most commonly due to a mutation in Type-I collagen,[72] which fulfills a variety of structural roles and is the most abundant protein in mammals.[73] The mutation causes a deformation in collagen's triple helix structure, which if not naturally destroyed, leads to abnormal and weakened bone tissue.[74] In 2005, Folding@home tested a new quantum mechanical method that improved upon prior simulation methods, and which may be useful for future computing studies of collagen.[75] Although researchers have used Folding@home to study collagen folding and misfolding, the interest stands as a pilot project compared to Alzheimer's and Huntington's research.[31]

Viruses

Folding@home is assisting in research towards preventing some viruses, such as influenza and HIV, from recognizing and entering biological cells.[31] In 2011, Folding@home began simulations of the dynamics of the enzyme RNase H, a key component of HIV, to try to design drugs to deactivate it.[76] Folding@home has also been used to study membrane fusion, an essential event for viral infection and a wide range of biological functions. This fusion involves conformational changes of viral fusion proteins and protein docking,[32] but the exact molecular mechanisms behind fusion remain largely unknown.[77] Fusion events may consist of over a half million atoms interacting for hundreds of microseconds. This complexity limits typical computer simulations to about ten thousand atoms over tens of nanoseconds: a difference of several orders of magnitude.[51] The development of models to predict the mechanisms of membrane fusion will assist in the scientific understanding of how to target the process with antiviral drugs.[78] In 2006, scientists applied Markov state models and the Folding@home network to discover two pathways for fusion and gain other mechanistic insights.[51]

Following detailed simulations from Folding@home of small cells known as vesicles, in 2007, the Pande lab introduced a new computing method to measure the topology of its structural changes during fusion.[79] In 2009, researchers used Folding@home to study mutations of influenza hemagglutinin, a protein that attaches a virus to its host cell and assists with viral entry. Mutations to hemagglutinin affect how well the protein binds to a host's cell surface receptor molecules, which determines how infective the virus strain is to the host organism. Knowledge of the effects of hemagglutinin mutations assists in the development of antiviral drugs.[80][81] As of 2012, Folding@home continues to simulate the folding and interactions of hemagglutinin, complementing experimental studies at the University of Virginia.[31][82]

In March 2020, Folding@home launched a program to assist researchers around the world who are working on finding a cure and learning more about the coronavirus pandemic. The initial wave of projects simulate potentially druggable protein targets from SARS-CoV-2 virus, and the related SARS-CoV virus, about which there is significantly more data available.[83][84][85]

Drug design

Drugs function by binding to specific locations on target molecules and causing some desired change, such as disabling a target or causing a conformational change. Ideally, a drug should act very specifically, and bind only to its target without interfering with other biological functions. However, it is difficult to precisely determine where and how tightly two molecules will bind. Due to limits in computing power, current in silico methods usually must trade speed for accuracy; e.g., use rapid protein docking methods instead of computationally costly free energy calculations. Folding@home's computing performance allows researchers to use both methods, and evaluate their efficiency and reliability.[35][86][87] Computer-assisted drug design has the potential to expedite and lower the costs of drug discovery.[34] In 2010, Folding@home used MSMs and free energy calculations to predict the native state of the villin protein to within 1.8 angstrom (Å) root mean square deviation (RMSD) from the crystalline structure experimentally determined through X-ray crystallography. This accuracy has implications to future protein structure prediction methods, including for intrinsically unstructured proteins.[51] Scientists have used Folding@home to research drug resistance by studying vancomycin, an antibiotic drug of last resort, and beta-lactamase, a protein that can break down antibiotics like penicillin.[88][89]

Chemical activity occurs along a protein's active site. Traditional drug design methods involve tightly binding to this site and blocking its activity, under the assumption that the target protein exists in one rigid structure. However, this approach works for approximately only 15% of all proteins. Proteins contain allosteric sites which, when bound to by small molecules, can alter a protein's conformation and ultimately affect the protein's activity. These sites are attractive drug targets, but locating them is very computationally costly. In 2012, Folding@home and MSMs were used to identify allosteric sites in three medically relevant proteins: beta-lactamase, interleukin-2, and RNase H.[89][90]

Approximately half of all known antibiotics interfere with the workings of a bacteria's ribosome, a large and complex biochemical machine that performs protein biosynthesis by translating messenger RNA into proteins. Macrolide antibiotics clog the ribosome's exit tunnel, preventing synthesis of essential bacterial proteins. In 2007, the Pande lab received a grant to study and design new antibiotics.[31] In 2008, they used Folding@home to study the interior of this tunnel and how specific molecules may affect it.[91] The full structure of the ribosome was determined only as of 2011, and Folding@home has also simulated ribosomal proteins, as many of their functions remain largely unknown.[92]

Patterns of participation

Like other distributed computing projects, Folding@home is an online citizen science project. In these projects non-specialists contribute computer processing power or help to analyze data produced by professional scientists. Participants receive little or no obvious reward.

Research has been carried out into the motivations of citizen scientists and most of these studies have found that participants are motivated to take part because of altruistic reasons; that is, they want to help scientists and make a contribution to the advancement of their research.[93][94][95][96] Many participants in citizen science have an underlying interest in the topic of the research and gravitate towards projects that are in disciplines of interest to them. Folding@home is no different in that respect.[97] Research carried out recently on over 400 active participants revealed that they wanted to help make a contribution to research and that many had friends or relatives affected by the diseases that the Folding@home scientists investigate.

Folding@home attracts participants who are computer hardware enthusiasts. These groups bring considerable expertise to the project and are able to build computers with advanced processing power.[98]Шаблон:Request quotation Other distributed computing projects attract these types of participants and projects are often used to benchmark the performance of modified computers, and this aspect of the hobby is accommodated through the competitive nature of the project. Individuals and teams can compete to see who can process the most computer processing units (CPUs).

This latest research on Folding@home involving interview and ethnographic observation of online groups showed that teams of hardware enthusiasts can sometimes work together, sharing best practice with regard to maximizing processing output. Such teams can become communities of practice, with a shared language and online culture. This pattern of participation has been observed in other distributed computing projects.[99][100]

Another key observation of Folding@home participants is that many are male.[97] This has also been observed in other distributed projects. Furthermore, many participants work in computer and technology-based jobs and careers.[97][101][102]

Not all Folding@home participants are hardware enthusiasts. Many participants run the project software on unmodified machines and do take part competitively. By January 2020, the number of users was down to 30,000.[103] However, it is difficult to ascertain what proportion of participants are hardware enthusiasts. Although, according to the project managers, the contribution of the enthusiast community is substantially larger in terms of processing power.[104]

Performance

Файл:Folding@home and Supercomputer Computational Powers.png
Computing power of Folding@home and the fastest supercomputer from April 2004 to October 2012. Between June 2007 and June 2011, Folding@home (red) exceeded the performance of Top500's fastest supercomputer (black). However it was eclipsed by K computer in November 2011 and Blue Gene/Q in June 2012.

Supercomputer FLOPS performance is assessed by running the legacy LINPACK benchmark. This short-term testing has difficulty in accurately reflecting sustained performance on real-world tasks because LINPACK more efficiently maps to supercomputer hardware. Computing systems vary in architecture and design, so direct comparison is difficult. Despite this, FLOPS remain the primary speed metric used in supercomputing.[105]Шаблон:Request quotation In contrast, Folding@home determines its FLOPS using wall-clock time by measuring how much time its work units take to complete.[106]

On September 16, 2007, due in large part to the participation of PlayStation 3 consoles, the Folding@home project officially attained a sustained performance level higher than one native petaFLOPS, becoming the first computing system of any kind to do so.[107][108] Top500's fastest supercomputer at the time was BlueGene/L, at 0.280 petaFLOPS.[109] The following year, on May 7, 2008, the project attained a sustained performance level higher than two native petaFLOPS,[110] followed by the three and four native petaFLOPS milestones in August 2008[111][112] and September 28, 2008 respectively.[113] On February 18, 2009, Folding@home achieved five native petaFLOPS,[114][115] and was the first computing project to meet these five levels.[116][117] In comparison, November 2008's fastest supercomputer was IBM's Roadrunner at 1.105 petaFLOPS.[118] On November 10, 2011, Folding@home's performance exceeded six native petaFLOPS with the equivalent of nearly eight x86 petaFLOPS.[108][119] In mid-May 2013, Folding@home attained over seven native petaFLOPS, with the equivalent of 14.87 x86 petaFLOPS. It then reached eight native petaFLOPS on June 21, followed by nine on September 9 of that year, with 17.9 x86 petaFLOPS.[120] On May 11, 2016 Folding@home announced that it was moving towards reaching the 100 x86 petaFLOPS mark.[121]

Further use grew from increased awareness and participation in the project from the coronavirus pandemic in 2020. On March 20, 2020 Folding@home announced via Twitter that it was running with over 470 native petaFLOPS,[122] the equivalent of 958 x86 petaFLOPS.[123] By March 25 it reached 768 petaFLOPS, or 1.5 x86 exaFLOPS, making it the first exaFLOP computing system.[124]

Шаблон:As of, the computing power of Folding@home stands at 28 petaFLOPS, or 54 x86 petaFLOPS.[125]

Points

Similarly to other distributed computing projects, Folding@home quantitatively assesses user computing contributions to the project through a credit system.[126] All units from a given protein project have uniform base credit, which is determined by benchmarking one or more work units from that project on an official reference machine before the project is released.[126] Each user receives these base points for completing every work unit, though through the use of a passkey they can receive added bonus points for reliably and rapidly completing units which are more demanding computationally or have a greater scientific priority.[127][128] Users may also receive credit for their work by clients on multiple machines.[129] This point system attempts to align awarded credit with the value of the scientific results.[126]

Users can register their contributions under a team, which combine the points of all their members. A user can start their own team, or they can join an existing team. In some cases, a team may have their own community-driven sources of help or recruitment such as an Internet forum.[130] The points can foster friendly competition between individuals and teams to compute the most for the project, which can benefit the folding community and accelerate scientific research.[126][131][132] Individual and team statistics are posted on the Folding@home website.[126]

If a user does not form a new team, or does not join an existing team, that user automatically becomes part of a "Default" team. This "Default" team has a team number of "0". Statistics are accumulated for this "Default" team as well as for specially named teams.

Software

Folding@home software at the user's end involves three primary components: work units, cores, and a client.

Work units

A work unit is the protein data that the client is asked to process. Work units are a fraction of the simulation between the states in a Markov model. After the work unit has been downloaded and completely processed by a volunteer's computer, it is returned to Folding@home servers, which then award the volunteer the credit points. This cycle repeats automatically.[131] All work units have associated deadlines, and if this deadline is exceeded, the user may not get credit and the unit will be automatically reissued to another participant. As protein folding occurs serially, and many work units are generated from their predecessors, this allows the overall simulation process to proceed normally if a work unit is not returned after a reasonable period of time. Due to these deadlines, the minimum system requirement for Folding@home is a Pentium 3 450 MHz CPU with Streaming SIMD Extensions (SSE).[129] However, work units for high-performance clients have a much shorter deadline than those for the uniprocessor client, as a major part of the scientific benefit is dependent on rapidly completing simulations.[133]

Before public release, work units go through several quality assurance steps to keep problematic ones from becoming fully available. These testing stages include internal, beta, and advanced, before a final full release across Folding@home.[134] Folding@home's work units are normally processed only once, except in the rare event that errors occur during processing. If this occurs for three different users, the unit is automatically pulled from distribution.[135][136] The Folding@home support forum can be used to differentiate between issues arising from problematic hardware and bad work units.[137]

Cores

Шаблон:Main Specialized molecular dynamics programs, referred to as "FahCores" and often abbreviated "cores", perform the calculations on the work unit as a background process. A large majority of Folding@home's cores are based on GROMACS,[131] one of the fastest and most popular molecular dynamics software packages, which largely consists of manually optimized assembly language code and hardware optimizations.[138][139] Although GROMACS is open-source software and there is a cooperative effort between the Pande lab and GROMACS developers, Folding@home uses a closed-source license to help ensure data validity.[140] Less active cores include ProtoMol and SHARPEN. Folding@home has used AMBER, CPMD, Desmond, and TINKER, but these have since been retired and are no longer in active service.[141][142][143] Some of these cores perform explicit solvation calculations in which the surrounding solvent (usually water) is modeled atom-by-atom; while others perform implicit solvation methods, where the solvent is treated as a mathematical continuum.[144][145] The core is separate from the client to enable the scientific methods to be updated automatically without requiring a client update. The cores periodically create calculation checkpoints so that if they are interrupted they can resume work from that point upon startup.[131]

Client

Файл:Folding@home Fedora25.png
Folding@home running on Fedora 25

A Folding@home participant installs a client program on their personal computer. The user interacts with the client, which manages the other software components in the background. Through the client, the user may pause the folding process, open an event log, check the work progress, or view personal statistics.[146] The computer clients run continuously in the background at a very low priority, using idle processing power so that normal computer use is unaffected.[129] The maximum CPU use can be adjusted via client settings.[146][147] The client connects to a Folding@home server and retrieves a work unit and may also download the appropriate core for the client's settings, operating system, and the underlying hardware architecture. After processing, the work unit is returned to the Folding@home servers. Computer clients are tailored to uniprocessor and multi-core processor systems, and graphics processing units. The diversity and power of each hardware architecture provides Folding@home with the ability to efficiently complete many types of simulations in a timely manner (in a few weeks or months rather than years), which is of significant scientific value. Together, these clients allow researchers to study biomedical questions formerly considered impractical to tackle computationally.[35][131][133]

Professional software developers are responsible for most of Folding@home's code, both for the client and server-side. The development team includes programmers from Nvidia, ATI, Sony, and Cauldron Development.[148] Clients can be downloaded only from the official Folding@home website or its commercial partners, and will only interact with Folding@home computer files. They will upload and download data with Folding@home's data servers (over port 8080, with 80 as an alternate), and the communication is verified using 2048-bit digital signatures.[129][149] While the client's graphical user interface (GUI) is open-source,[150] the client is proprietary software citing security and scientific integrity as the reasons.[151][152][153]

However, this rationale of using proprietary software is disputed since while the license could be enforceable in the legal domain retrospectively, it does not practically prevent the modification (also known as patching) of the executable binary files. Likewise, binary-only distribution does not prevent the malicious modification of executable binary-code, either through a man-in-the-middle attack while being downloaded via the internet,[154] or by the redistribution of binaries by a third-party that have been previously modified either in their binary state (i.e. patched),[155] or by decompiling[156] and recompiling them after modification.[157][158] These modifications are possible unless the binary files – and the transport channel – are signed and the recipient person/system is able to verify the digital signature, in which case unwarranted modifications should be detectable, but not always.[159] Either way, since in the case of Folding@home the input data and output result processed by the client-software are both digitally signed,[129][149] the integrity of work can be verified independently from the integrity of the client software itself.

Folding@home uses the Cosm software libraries for networking.[131][148] Folding@home was launched on October 1, 2000, and was the first distributed computing project aimed at bio-molecular systems.[160] Its first client was a screensaver, which would run while the computer was not otherwise in use.[161][162] In 2004, the Pande lab collaborated with David P. Anderson to test a supplemental client on the open-source BOINC framework. This client was released to closed beta in April 2005;[163] however, the method became unworkable and was shelved in June 2006.[164]

Graphics processing units

The specialized hardware of graphics processing units (GPU) is designed to accelerate rendering of 3-D graphics applications such as video games and can significantly outperform CPUs for some types of calculations. GPUs are one of the most powerful and rapidly growing computing platforms, and many scientists and researchers are pursuing general-purpose computing on graphics processing units (GPGPU). However, GPU hardware is difficult to use for non-graphics tasks and usually requires significant algorithm restructuring and an advanced understanding of the underlying architecture.[165] Such customization is challenging, more so to researchers with limited software development resources. Folding@home uses the open-source OpenMM library, which uses a bridge design pattern with two application programming interface (API) levels to interface molecular simulation software to an underlying hardware architecture. With the addition of hardware optimizations, OpenMM-based GPU simulations need no significant modification but achieve performance nearly equal to hand-tuned GPU code, and greatly outperform CPU implementations.[144][166]

Before 2010, the computing reliability of GPGPU consumer-grade hardware was largely unknown, and circumstantial evidence related to the lack of built-in error detection and correction in GPU memory raised reliability concerns. In the first large-scale test of GPU scientific accuracy, a 2010 study of over 20,000 hosts on the Folding@home network detected soft errors in the memory subsystems of two-thirds of the tested GPUs. These errors strongly correlated to board architecture, though the study concluded that reliable GPU computing was very feasible as long as attention is paid to the hardware traits, such as software-side error detection.[167]

The first generation of Folding@home's GPU client (GPU1) was released to the public on October 2, 2006,[164] delivering a 20–30 times speedup for some calculations over its CPU-based GROMACS counterparts.[168] It was the first time GPUs had been used for either distributed computing or major molecular dynamics calculations.[169][170] GPU1 gave researchers significant knowledge and experience with the development of GPGPU software, but in response to scientific inaccuracies with DirectX, on April 10, 2008, it was succeeded by GPU2, the second generation of the client.[168][171] Following the introduction of GPU2, GPU1 was officially retired on June 6.[168] Compared to GPU1, GPU2 was more scientifically reliable and productive, ran on ATI and CUDA-enabled Nvidia GPUs, and supported more advanced algorithms, larger proteins, and real-time visualization of the protein simulation.[172][173] Following this, the third generation of Folding@home's GPU client (GPU3) was released on May 25, 2010. While backward compatible with GPU2, GPU3 was more stable, efficient, and flexibile in its scientific abilities,[174] and used OpenMM on top of an OpenCL framework.[174][175] Although these GPU3 clients did not natively support the operating systems Linux and macOS, Linux users with Nvidia graphics cards were able to run them through the Wine software application.[176][177] GPUs remain Folding@home's most powerful platform in FLOPS. As of November 2012, GPU clients account for 87% of the entire project's x86 FLOPS throughput.[178]

Native support for Nvidia and AMD graphics cards under Linux was introduced with FahCore 17, which uses OpenCL rather than CUDA.[179]

PlayStation 3

Шаблон:Further

Файл:LifeWithPlayStation Folding.jpg
The PlayStation 3's Life With PlayStation client displayed a 3-D animation of the protein being folded

From March 2007 until November 2012, Folding@home took advantage of the computing power of PlayStation 3s. At the time of its inception, its main streaming Cell processor delivered a 20 times speed increase over PCs for some calculations, processing power which could not be found on other systems such as the Xbox 360.[35][180] The PS3's high speed and efficiency introduced other opportunities for worthwhile optimizations according to Amdahl's law, and significantly changed the tradeoff between computing efficiency and overall accuracy, allowing the use of more complex molecular models at little added computing cost.[181] This allowed Folding@home to run biomedical calculations that would have been otherwise infeasible computationally.[182]

The PS3 client was developed in a collaborative effort between Sony and the Pande lab and was first released as a standalone client on March 23, 2007.[35][183] Its release made Folding@home the first distributed computing project to use PS3s.[184] On September 18 of the following year, the PS3 client became a channel of Life with PlayStation on its launch.[185][186] In the types of calculations it can perform, at the time of its introduction, the client fit in between a CPU's flexibility and a GPU's speed.[131] However, unlike clients running on personal computers, users were unable to perform other activities on their PS3 while running Folding@home.[182] The PS3's uniform console environment made technical support easier and made Folding@home more user friendly.[35] The PS3 also had the ability to stream data quickly to its GPU, which was used for real-time atomic-level visualizing of the current protein dynamics.[181]

On November 6, 2012, Sony ended support for the Folding@home PS3 client and other services available under Life with PlayStation. Over its lifetime of five years and seven months, more than 15 million users contributed over 100 million hours of computing to Folding@home, greatly assisting the project with disease research. Following discussions with the Pande lab, Sony decided to terminate the application. Pande considered the PlayStation 3 client a "game changer" for the project.[187][188][189]

Multi-core processing client

Folding@home can use the parallel computing abilities of modern multi-core processors. The ability to use several CPU cores simultaneously allows completing the full simulation far faster. Working together, these CPU cores complete single work units proportionately faster than the standard uniprocessor client. This method is scientifically valuable because it enables much longer simulation trajectories to be performed in the same amount of time, and reduces the traditional difficulties of scaling a large simulation to many separate processors.[190] A 2007 publication in the Journal of Molecular Biology relied on multi-core processing to simulate the folding of part of the villin protein approximately 10 times longer than was possible with a single-processor client, in agreement with experimental folding rates.[191]

In November 2006, first-generation symmetric multiprocessing (SMP) clients were publicly released for open beta testing, referred to as SMP1.[164] These clients used Message Passing Interface (MPI) communication protocols for parallel processing, as at that time the GROMACS cores were not designed to be used with multiple threads.[133] This was the first time a distributed computing project had used MPI.[192] Although the clients performed well in Unix-based operating systems such as Linux and macOS, they were troublesome under Windows.[190][192] On January 24, 2010, SMP2, the second generation of the SMP clients and the successor to SMP1, was released as an open beta and replaced the complex MPI with a more reliable thread-based implementation.[128][148]

SMP2 supports a trial of a special category of bigadv work units, designed to simulate proteins that are unusually large and computationally intensive and have a great scientific priority. These units originally required a minimum of eight CPU cores,[193] which was raised to sixteen later, on February 7, 2012.[194] Along with these added hardware requirements over standard SMP2 work units, they require more system resources such as random-access memory (RAM) and Internet bandwidth. In return, users who run these are rewarded with a 20% increase over SMP2's bonus point system.[195] The bigadv category allows Folding@home to run especially demanding simulations for long times that had formerly required use of supercomputing clusters and could not be performed anywhere else on Folding@home.[193] Many users with hardware able to run bigadv units have later had their hardware setup deemed ineligible for bigadv work units when CPU core minimums were increased, leaving them only able to run the normal SMP work units. This frustrated many users who invested significant amounts of money into the program only to have their hardware be obsolete for bigadv purposes shortly after. As a result, Pande announced in January 2014 that the bigadv program would end on January 31, 2015.[196]

V7

Файл:F@h v7 novice shot.png
A sample image of the V7 client in Novice mode running under Windows 7. In addition to a variety of controls and user details, V7 presents work unit information, such as its state, calculation progress, ETA, credit points, identification numbers, and description.

The V7 client is the seventh and latest generation of the Folding@home client software, and is a full rewrite and unification of the prior clients for Windows, macOS, and Linux operating systems.[197][198] It was released on March 22, 2012.[199] Like its predecessors, V7 can run Folding@home in the background at a very low priority, allowing other applications to use CPU resources as they need. It is designed to make the installation, start-up, and operation more user-friendly for novices, and offer greater scientific flexibility to researchers than prior clients.[200] V7 uses Trac for managing its bug tickets so that users can see its development process and provide feedback.[198]

V7 consists of four integrated elements. The user typically interacts with V7's open-source GUI, named FAHControl.[150][201] This has Novice, Advanced, and Expert user interface modes, and has the ability to monitor, configure, and control many remote folding clients from one computer. FAHControl directs FAHClient, a back-end application that in turn manages each FAHSlot (or slot). Each slot acts as replacement for the formerly distinct Folding@home v6 uniprocessor, SMP, or GPU computer clients, as it can download, process, and upload work units independently. The FAHViewer function, modeled after the PS3's viewer, displays a real-time 3-D rendering, if available, of the protein currently being processed.[197][198]

Google Chrome

In 2014, a client for the Google Chrome and Chromium web browsers was released, allowing users to run Folding@home in their web browser. The client used Google's Native Client (NaCl) feature on Chromium-based web browsers to run the Folding@home code at near-native speed in a sandbox on the user's machine.[202] Due to the phasing out of NaCL and changes at Folding@home, the web client was permanently shut down in June 2019.[203]

Android

In July 2015, a client for Android mobile phones was released on Google Play for devices running Android 4.4 KitKat or newer.[204][205]

On February 16, 2018, the Android client, which was offered in cooperation with Sony, was removed from Google Play. Plans were announced to offer an open source alternative in the future.[206]

Comparison to other molecular simulators

Rosetta@home is a distributed computing project aimed at protein structure prediction and is one of the most accurate tertiary structure predictors.[207][208] The conformational states from Rosetta's software can be used to initialize a Markov state model as starting points for Folding@home simulations.[21] Conversely, structure prediction algorithms can be improved from thermodynamic and kinetic models and the sampling aspects of protein folding simulations.[209] As Rosetta only tries to predict the final folded state, and not how folding proceeds, Rosetta@home and Folding@home are complementary and address very different molecular questions.[21][210]

Anton is a special-purpose supercomputer built for molecular dynamics simulations. In October 2011, Anton and Folding@home were the two most powerful molecular dynamics systems.[211] Anton is unique in its ability to produce single ultra-long computationally costly molecular trajectories,[212] such as one in 2010 which reached the millisecond range.[213][214] These long trajectories may be especially helpful for some types of biochemical problems.[215][216] However, Anton does not use Markov state models (MSM) for analysis. In 2011, the Pande lab constructed a MSM from two 100-µs Anton simulations and found alternative folding pathways that were not visible through Anton's traditional analysis. They concluded that there was little difference between MSMs constructed from a limited number of long trajectories or one assembled from many shorter trajectories.[212] In June 2011 Folding@home added sampling of an Anton simulation in an effort to better determine how its methods compare to Anton's.[217][218] However, unlike Folding@home's shorter trajectories, which are more amenable to distributed computing and other parallelizing methods, longer trajectories do not require adaptive sampling to sufficiently sample the protein's phase space. Due to this, it is possible that a combination of Anton's and Folding@home's simulation methods would provide a more thorough sampling of this space.[212]

See also

Шаблон:Portal Шаблон:Div col

Шаблон:Div col end

References

Шаблон:Reflist

Sources

External links

Шаблон:Commons category

Шаблон:Spoken Wikipedia

Шаблон:Health software Шаблон:PlayStation 3

Шаблон:Use mdy dates

  1. Шаблон:Harvnb: "Folding@home (FAH or F@h) is a distributed computing project for simulating protein dynamics, including the process of protein folding and the movements of proteins implicated in a variety of diseases. It brings together citizen scientists who volunteer to run simulations of protein dynamics on their personal computers. Insights from this data are helping scientists to better understand biology, and providing new opportunities for developing therapeutics."
  2. Ошибка цитирования Неверный тег <ref>; для сносок FAH leadership change не указан текст
  3. 3,0 3,1 3,2 Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/j.ymeth.2010.06.002 не указан текст
  4. Шаблон:Harvnb: "Since the start of the COVID-19 pandemic, Folding@home has seen a significant surge in downloads, a clear indication that people around the world are concerned about doing their part to help researchers find a remedy to this virus," said Dr. Sina Rabbany, dean of the DeMatteis School."
  5. Шаблон:Cite web
  6. Шаблон:Cite web
  7. 7,0 7,1 7,2 Ошибка цитирования Неверный тег <ref>; для сносок 10.1021/ja9090353 не указан текст
  8. Ошибка цитирования Неверный тег <ref>; для сносок 10.1073/pnas.1003962107 не указан текст
  9. 9,0 9,1 Ошибка цитирования Неверный тег <ref>; для сносок 10.1038/nature01160 не указан текст
  10. Ошибка цитирования Неверный тег <ref>; для сносок 10.1371/journal.pcbi.1000452 не указан текст
  11. Ошибка цитирования Неверный тег <ref>; для сносок 10.1126/science.309.5731.78b не указан текст
  12. 12,0 12,1 12,2 Ошибка цитирования Неверный тег <ref>; для сносок 10.1002/iub.117 не указан текст
  13. 13,0 13,1 Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/j.abb.2007.05.014 не указан текст
  14. 14,0 14,1 Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/j.cbpa.2008.02.011 не указан текст
  15. Ошибка цитирования Неверный тег <ref>; для сносок 10.1146/annurev.biophys.34.040204.144447 не указан текст
  16. Ошибка цитирования Неверный тег <ref>; для сносок 978-1-58603-796-3 не указан текст
  17. Ошибка цитирования Неверный тег <ref>; для сносок 10.1002/bip.10219 не указан текст
  18. 18,0 18,1 18,2 Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/j.sbi.2010.10.006 не указан текст
  19. Ошибка цитирования Неверный тег <ref>; для сносок 10.1137/06065146X не указан текст
  20. Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/j.sbi.2011.12.001 не указан текст
  21. 21,0 21,1 21,2 Ошибка цитирования Неверный тег <ref>; для сносок Simulation FAQ не указан текст
  22. Ошибка цитирования Неверный тег <ref>; для сносок 10.1021/ct900620b не указан текст
  23. Ошибка цитирования Неверный тег <ref>; для сносок typepad: how far FAH has come не указан текст
  24. Ошибка цитирования Неверный тег <ref>; для сносок 10.1073/pnas.1010880108 не указан текст
  25. Ошибка цитирования Неверный тег <ref>; для сносок 10.3390/ijms11125292 не указан текст
  26. Ошибка цитирования Неверный тег <ref>; для сносок 2010 KPS award не указан текст
  27. Ошибка цитирования Неверный тег <ref>; для сносок MSMBuilder source не указан текст
  28. Ошибка цитирования Неверный тег <ref>; для сносок Biophysical society names recipients не указан текст
  29. Ошибка цитирования Неверный тег <ref>; для сносок FAH Awards не указан текст
  30. Ошибка цитирования Неверный тег <ref>; для сносок Protein Misfolding Diseases не указан текст
  31. 31,0 31,1 31,2 31,3 31,4 31,5 31,6 31,7 31,8 Ошибка цитирования Неверный тег <ref>; для сносок diseases FAQ не указан текст
  32. 32,0 32,1 Ошибка цитирования Неверный тег <ref>; для сносок 978-0-340-66316-5 не указан текст
  33. Ошибка цитирования Неверный тег <ref>; для сносок 10.1038/nature02265 не указан текст
  34. 34,0 34,1 Ошибка цитирования Неверный тег <ref>; для сносок 10.1093/bib/bbp023 не указан текст
  35. 35,0 35,1 35,2 35,3 35,4 35,5 Ошибка цитирования Неверный тег <ref>; для сносок Press FAQ не указан текст
  36. Ошибка цитирования Неверный тег <ref>; для сносок forum: 7808/7809 to FAH не указан текст
  37. Ошибка цитирования Неверный тег <ref>; для сносок 10.1073/pnas.0608256104 не указан текст
  38. Ошибка цитирования Неверный тег <ref>; для сносок 10.1021/ja908369h не указан текст
  39. 39,0 39,1 Ошибка цитирования Неверный тег <ref>; для сносок typepad: Simbios не указан текст
  40. Ошибка цитирования Неверный тег <ref>; для сносок papers for free не указан текст
  41. Ошибка цитирования Неверный тег <ref>; для сносок 10.1038/sj.embor.7400108 не указан текст
  42. Ошибка цитирования Неверный тег <ref>; для сносок Pronk et al, 2011 не указан текст
  43. Ошибка цитирования Неверный тег <ref>; для сносок Copernicus download не указан текст
  44. Ошибка цитирования Неверный тег <ref>; для сносок papers не указан текст
  45. Ошибка цитирования Неверный тег <ref>; для сносок 10.2119/2007-00100.Irvine не указан текст
  46. Ошибка цитирования Неверный тег <ref>; для сносок 10.1001/archneurol.2007.56 не указан текст
  47. Ошибка цитирования Неверный тег <ref>; для сносок 10.1074/jbc.R800036200 не указан текст
  48. 48,0 48,1 Ошибка цитирования Неверный тег <ref>; для сносок 10.1063/1.3010881 не указан текст
  49. 49,0 49,1 Ошибка цитирования Неверный тег <ref>; для сносок 10.1371/journal.pone.0021776 не указан текст
  50. Ошибка цитирования Неверный тег <ref>; для сносок 10.1007/s12013-011-9200-x не указан текст
  51. 51,0 51,1 51,2 51,3 Ошибка цитирования Неверный тег <ref>; для сносок 10.1038/cr.2010.57 не указан текст
  52. Ошибка цитирования Неверный тег <ref>; для сносок typepad: possible alz. drug не указан текст
  53. Ошибка цитирования Неверный тег <ref>; для сносок 10.1021/jm201332p не указан текст
  54. Ошибка цитирования Неверный тег <ref>; для сносок forum: 6871 не указан текст
  55. Ошибка цитирования Неверный тег <ref>; для сносок description: 6571 не указан текст
  56. Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/S0140-6736(07)60111-1 не указан текст
  57. Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/j.jmb.2009.01.032 не указан текст
  58. Ошибка цитирования Неверный тег <ref>; для сносок 10.1038/nchembio.279 не указан текст
  59. Ошибка цитирования Неверный тег <ref>; для сносок forum: 8021 in beta не указан текст
  60. Ошибка цитирования Неверный тег <ref>; для сносок 10.1126/science.1905840 не указан текст
  61. Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/j.jmb.2004.10.083 не указан текст
  62. Ошибка цитирования Неверный тег <ref>; для сносок FAH publishes cancer results не указан текст
  63. Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/j.jmb.2005.12.083 не указан текст
  64. Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/j.biopha.2011.04.025 не указан текст
  65. Ошибка цитирования Неверный тег <ref>; для сносок typepad: nanomedicine ce не указан текст
  66. Ошибка цитирования Неверный тег <ref>; для сносок typepad: protomol b4 не указан текст
  67. Ошибка цитирования Неверный тег <ref>; для сносок description: 180 не указан текст
  68. Ошибка цитирования Неверный тег <ref>; для сносок forum: 7600 in beta не указан текст
  69. Ошибка цитирования Неверный тег <ref>; для сносок description: 7600 не указан текст
  70. Ошибка цитирования Неверный тег <ref>; для сносок scientists boost IL-2 potency не указан текст
  71. Ошибка цитирования Неверный тег <ref>; для сносок 10.1038/nature10975 не указан текст
  72. Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/S0140-6736(04)16051-0 не указан текст
  73. Ошибка цитирования Неверный тег <ref>; для сносок 978-0-387-73905-2 не указан текст
  74. Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/j.bpj.2009.04.059 не указан текст
  75. Ошибка цитирования Неверный тег <ref>; для сносок 10.1002/jcc.20301 не указан текст
  76. Ошибка цитирования Неверный тег <ref>; для сносок forum: 10125 не указан текст
  77. Ошибка цитирования Неверный тег <ref>; для сносок 10.1039/c0cs00115e не указан текст
  78. Ошибка цитирования Неверный тег <ref>; для сносок Peter Kasson не указан текст
  79. Ошибка цитирования Неверный тег <ref>; для сносок 10.1093/bioinformatics/btm250 не указан текст
  80. Ошибка цитирования Неверный тег <ref>; для сносок 10.1021/ja904557w не указан текст
  81. Ошибка цитирования Неверный тег <ref>; для сносок 19209725, 2811693 не указан текст
  82. Ошибка цитирования Неверный тег <ref>; для сносок typepad: kasson update не указан текст
  83. Шаблон:Cite web
  84. Шаблон:Cite web
  85. Шаблон:Cite web
  86. Ошибка цитирования Неверный тег <ref>; для сносок typepad: drug design methods не указан текст
  87. Ошибка цитирования Неверный тег <ref>; для сносок 10.1063/1.2221680 не указан текст
  88. Ошибка цитирования Неверный тег <ref>; для сносок description: 10721 не указан текст
  89. 89,0 89,1 Ошибка цитирования Неверный тег <ref>; для сносок typepad: drug targets не указан текст
  90. Ошибка цитирования Неверный тег <ref>; для сносок 10.1073/pnas.1209309109 не указан текст
  91. Ошибка цитирования Неверный тег <ref>; для сносок 10.1073/pnas.0801795105 не указан текст
  92. Ошибка цитирования Неверный тег <ref>; для сносок description: 5765 не указан текст
  93. Шаблон:Cite journal
  94. Шаблон:Cite book
  95. Шаблон:Cite book
  96. Шаблон:Cite journal
  97. 97,0 97,1 97,2 Шаблон:Cite journal
  98. Шаблон:Cite journal
  99. Шаблон:Cite journal
  100. Шаблон:Cite journal
  101. Шаблон:Cite web
  102. Шаблон:Cite journal
  103. Шаблон:Cite web
  104. Шаблон:Cite book
  105. Шаблон:Harvnb
  106. Шаблон:Harvnb: "Wall clock time is in the end the only thing that matters and that's why we benchmark on wall clock (and why in our papers, we emphasize wall clock)."
  107. Ошибка цитирования Неверный тег <ref>; для сносок typepad: crossing 1 PF не указан текст
  108. 108,0 108,1 Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/j.cub.2012.01.008 не указан текст
  109. Ошибка цитирования Неверный тег <ref>; для сносок Top500 June 2007 не указан текст
  110. Ошибка цитирования Неверный тег <ref>; для сносок FAH reaches 2 PF не указан текст
  111. Ошибка цитирования Неверный тег <ref>; для сносок Nvidia-FAH milestone не указан текст
  112. Ошибка цитирования Неверный тег <ref>; для сносок 3 PF barrier не указан текст
  113. Ошибка цитирования Неверный тег <ref>; для сносок past 4 petaFLOPS не указан текст
  114. Ошибка цитирования Неверный тег <ref>; для сносок typepad: FAH passes 5 PF не указан текст
  115. Ошибка цитирования Неверный тег <ref>; для сносок crossing 5 PF barrier не указан текст
  116. Ошибка цитирования Неверный тег <ref>; для сносок Community Grid Computing не указан текст
  117. Ошибка цитирования Неверный тег <ref>; для сносок review of FAH не указан текст
  118. Ошибка цитирования Неверный тег <ref>; для сносок Top500 November 2008 не указан текст
  119. Ошибка цитирования Неверный тег <ref>; для сносок 6 petaFLOPS не указан текст
  120. Ошибка цитирования Неверный тег <ref>; для сносок FAH stats doc не указан текст
  121. Шаблон:Cite web
  122. Шаблон:Cite web
  123. Шаблон:Cite web
  124. Шаблон:Cite web
  125. Шаблон:Cite web
  126. 126,0 126,1 126,2 126,3 126,4 Ошибка цитирования Неверный тег <ref>; для сносок Points FAQ не указан текст
  127. Ошибка цитирования Неверный тег <ref>; для сносок Passkey FAQ не указан текст
  128. 128,0 128,1 Ошибка цитирования Неверный тег <ref>; для сносок SMP2 release не указан текст
  129. 129,0 129,1 129,2 129,3 129,4 Ошибка цитирования Неверный тег <ref>; для сносок Main FAQ не указан текст
  130. Ошибка цитирования Неверный тег <ref>; для сносок Extreme overclocking forum не указан текст
  131. 131,0 131,1 131,2 131,3 131,4 131,5 131,6 Ошибка цитирования Неверный тег <ref>; для сносок 10.1109/IPDPS.2009.5160922 не указан текст
  132. Ошибка цитирования Неверный тег <ref>; для сносок MaximumPC Chimp Challenge не указан текст
  133. 133,0 133,1 133,2 Ошибка цитирования Неверный тег <ref>; для сносок SMP FAQ не указан текст
  134. Ошибка цитирования Неверный тег <ref>; для сносок typepad: more transparency не указан текст
  135. Ошибка цитирования Неверный тег <ref>; для сносок forum: Gromacs cannot continue не указан текст
  136. Ошибка цитирования Неверный тег <ref>; для сносок forum: 6803(4,66,255) не указан текст
  137. Ошибка цитирования Неверный тег <ref>; для сносок forum: troubleshooting bad WUs не указан текст
  138. Ошибка цитирования Неверный тег <ref>; для сносок 10.1002/jcc.20703 не указан текст
  139. Ошибка цитирования Неверный тег <ref>; для сносок 10.1021/ct700301q не указан текст
  140. Ошибка цитирования Неверный тег <ref>; для сносок Gromacs FAQ не указан текст
  141. Ошибка цитирования Неверный тег <ref>; для сносок Open Source FAQ не указан текст
  142. Ошибка цитирования Неверный тег <ref>; для сносок FAQ index не указан текст
  143. Ошибка цитирования Неверный тег <ref>; для сносок typepad: update on new FahCores не указан текст
  144. 144,0 144,1 Ошибка цитирования Неверный тег <ref>; для сносок 10.1002/jcc.21209 не указан текст
  145. Ошибка цитирования Неверный тег <ref>; для сносок Petaflop FAQ не указан текст
  146. 146,0 146,1 Ошибка цитирования Неверный тег <ref>; для сносок Uni Guide не указан текст
  147. Ошибка цитирования Неверный тег <ref>; для сносок forum: can FAH damage PC? не указан текст
  148. 148,0 148,1 148,2 Ошибка цитирования Неверный тег <ref>; для сносок typepad: how does dev get done не указан текст
  149. 149,0 149,1 Ошибка цитирования Неверный тег <ref>; для сносок Uninstall не указан текст
  150. 150,0 150,1 Ошибка цитирования Неверный тег <ref>; для сносок FAHControl source code не указан текст
  151. Ошибка цитирования Неверный тег <ref>; для сносок FAH license не указан текст
  152. Ошибка цитирования Неверный тег <ref>; для сносок forum: FAH EULA не указан текст
  153. Ошибка цитирования Неверный тег <ref>; для сносок help ubuntu не указан текст
  154. Шаблон:Cite web
  155. Шаблон:Cite web
  156. probably using tools such as ERESI Шаблон:Webarchive
  157. Шаблон:Cite web
  158. Шаблон:Cite web
  159. Шаблон:Cite web
  160. Ошибка цитирования Неверный тег <ref>; для сносок 10.1039/C1CP22100K не указан текст
  161. Ошибка цитирования Неверный тег <ref>; для сносок 10.1126/science.290.5498.1903 не указан текст
  162. Ошибка цитирования Неверный тег <ref>; для сносок Executive summary не указан текст
  163. Ошибка цитирования Неверный тег <ref>; для сносок FAH for BOINC soon не указан текст
  164. 164,0 164,1 164,2 Ошибка цитирования Неверный тег <ref>; для сносок High-Per FAQ не указан текст
  165. Ошибка цитирования Неверный тег <ref>; для сносок 10.1111/j.1467-8659.2007.01012.x не указан текст
  166. Ошибка цитирования Неверный тег <ref>; для сносок 10.1109/MCSE.2010.27 не указан текст
  167. Ошибка цитирования Неверный тег <ref>; для сносок 10.1109/CCGRID.2010.84 не указан текст
  168. 168,0 168,1 168,2 Ошибка цитирования Неверный тег <ref>; для сносок ATI FAQ не указан текст
  169. Ошибка цитирования Неверный тег <ref>; для сносок typepad: GPU news не указан текст
  170. Ошибка цитирования Неверный тег <ref>; для сносок 978-3-642-14389-2 не указан текст
  171. Ошибка цитирования Неверный тег <ref>; для сносок typepad: GPU2 open beta не указан текст
  172. Ошибка цитирования Неверный тег <ref>; для сносок typepad: GPU2 goes live не указан текст
  173. Ошибка цитирования Неверный тег <ref>; для сносок typepad: GPU2 going well не указан текст
  174. 174,0 174,1 Ошибка цитирования Неверный тег <ref>; для сносок typepad: GPU3 prep не указан текст
  175. Ошибка цитирования Неверный тег <ref>; для сносок typepad: GPU3 open beta не указан текст
  176. Ошибка цитирования Неверный тег <ref>; для сносок forum: 7.1.38 released не указан текст
  177. Ошибка цитирования Неверный тег <ref>; для сносок forum: GPU3 headless guide не указан текст
  178. Ошибка цитирования Неверный тег <ref>; для сносок FAH osstats2 не указан текст
  179. Ошибка цитирования Неверный тег <ref>; для сносок forum: core17 Linux не указан текст
  180. Ошибка цитирования Неверный тег <ref>; для сносок Biotech 27 не указан текст
  181. 181,0 181,1 Ошибка цитирования Неверный тег <ref>; для сносок 10.1002/jcc.21054 не указан текст
  182. 182,0 182,1 Ошибка цитирования Неверный тег <ref>; для сносок cnn ps3 не указан текст
  183. Ошибка цитирования Неверный тег <ref>; для сносок PS3 to study cancer не указан текст
  184. Ошибка цитирования Неверный тег <ref>; для сносок PS3 research project не указан текст
  185. Ошибка цитирования Неверный тег <ref>; для сносок Life With PS3 live не указан текст
  186. Ошибка цитирования Неверный тег <ref>; для сносок typepad: life with PS не указан текст
  187. Ошибка цитирования Неверный тег <ref>; для сносок PS3 FAQ не указан текст
  188. Ошибка цитирования Неверный тег <ref>; для сносок PS3 4.30 update, drop F@h не указан текст
  189. Ошибка цитирования Неверный тег <ref>; для сносок LWP termination не указан текст
  190. 190,0 190,1 Ошибка цитирования Неверный тег <ref>; для сносок typepad: what does SMP do не указан текст
  191. Ошибка цитирования Неверный тег <ref>; для сносок 10.1016/j.jmb.2007.09.069 не указан текст
  192. 192,0 192,1 Ошибка цитирования Неверный тег <ref>; для сносок typepad: new client dev не указан текст
  193. 193,0 193,1 Ошибка цитирования Неверный тег <ref>; для сносок bigadv не указан текст
  194. Ошибка цитирования Неверный тег <ref>; для сносок typepad: update on bigadv-16 не указан текст
  195. Ошибка цитирования Неверный тег <ref>; для сносок typepad: bigadv points change не указан текст
  196. Шаблон:Cite web
  197. 197,0 197,1 Ошибка цитирования Неверный тег <ref>; для сносок V7 install guide не указан текст
  198. 198,0 198,1 198,2 Ошибка цитирования Неверный тег <ref>; для сносок typepad: V7 in open beta не указан текст
  199. Ошибка цитирования Неверный тег <ref>; для сносок typepad: v7 rollout не указан текст
  200. Ошибка цитирования Неверный тег <ref>; для сносок typepad: ATI core 16 released не указан текст
  201. Ошибка цитирования Неверный тег <ref>; для сносок Ticket #736 не указан текст
  202. Шаблон:Cite web
  203. Шаблон:Cite web
  204. Шаблон:Cite web
  205. Шаблон:Cite web
  206. Шаблон:Cite web
  207. Ошибка цитирования Неверный тег <ref>; для сносок 10.1002/prot.21804 не указан текст
  208. Ошибка цитирования Неверный тег <ref>; для сносок 10.1002/prot.22210 не указан текст
  209. Ошибка цитирования Неверный тег <ref>; для сносок 10.1371/journal.pone.0005840 не указан текст
  210. Ошибка цитирования Неверный тег <ref>; для сносок F@H vs R@h не указан текст
  211. Ошибка цитирования Неверный тег <ref>; для сносок typepad: comparison with Anton не указан текст
  212. 212,0 212,1 212,2 Ошибка цитирования Неверный тег <ref>; для сносок 10.1021/ja207470h не указан текст
  213. Ошибка цитирования Неверный тег <ref>; для сносок 10.1145/1654059.1654099 не указан текст
  214. Ошибка цитирования Неверный тег <ref>; для сносок 10.1126/science.1187409 не указан текст
  215. Ошибка цитирования Неверный тег <ref>; для сносок 10.1145/1364782.1364802 не указан текст
  216. Ошибка цитирования Неверный тег <ref>; для сносок 10.1146/annurev-biophys-042910-155245 не указан текст
  217. Ошибка цитирования Неверный тег <ref>; для сносок forum: 7610/7611 in beta не указан текст
  218. Ошибка цитирования Неверный тег <ref>; для сносок description: 7610 не указан текст