BAC on HPC Systems Sample Clauses

BAC on HPC Systems. BAC computational method is based on classical MD simulations where the unit of parallelism involved is a few hundred cores, but runs hundreds to thousands of these at a time in order to perform “high throughput” calculations in support of drug discovery and personalised medicine (for advising on drug treatment for patients based on their genomic profile). In order to guarantee reproducibility of predictions, ensembles of replica MD calculations are performed for each method. Combining this approach with the necessity to screen multiple compounds, makes BAC a perfect example of replica computing pattern application, where a large number of copies of simulations are needed to produce statistically robust results. All replicas simulations, which may be parallel runs themselves, execute independently of each other, allowing BAC to reach excellent scalability also at high number of cores. It is a computational workflow which is data intensive and data driven in the sense of needing a large amount of data to initialise and produce tens or more of terabytes of output per run. In the case of replica compute applications such as BAC, weak scaling analysis provide useful information to demonstrate the ability to solve larger systems as the resources available increase. Figure 6 shows the result of a weak scaling analysis, performed by UCL on the Blue Waters (NCSA) supercomputer. The study consisted in the screening of sixteen drug candidates concurrently using thousands of multi-stage pipelines. The results demonstrated the almost perfect scaling of the code up to 33,280 cores under the conditions tested. The overhead measured, consisted in the adaptive sampling of the method used, and small overhead from the HTBAC framework. The latter depends on the number of protocols generated and increase linearly, however, as showed in the results presented, is always negligible compared to the total time of execution. Similar scaling has been demonstrated on other platforms such as Titan (ORNL) and for different protocols.
AutoNDA by SimpleDocs

Related to BAC on HPC Systems

  • Infrastructure (a) The Borrower has and will maintain a sufficient infrastructure to conduct its business as presently conducted and as contemplated to be conducted following its execution of this Agreement.

  • Drainage Systems (1) Clear culvert inlets, outlets, and sediment catching basins.

  • Electric Systems Are there any problems with electrical fuses, circuit breakers, outlets or wiring? Yes No. Unknown Comments:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Irrigation Systems The Project Area either has no irrigation system or a low-volume drip irrigation system. If a watering system is used, it is a drip irrigation system equipped with a filter, pressure regulator and emitters rated at twenty (20) gallons per hour (gph) or less. The system is maintained free of leaks and malfunctions. No spray irrigation is applied to the Project Area, including spray from irrigation systems adjacent to the Project Area.

  • Infrastructure Improvements The design, redevelopment and construction and completion of certain infrastructure improvements, including sewer, stormwater, electrical and water main improvements, along with other similar improvements.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Unbundled Sub-Loop Concentration System (USLC 2.9.1 Where facilities permit and where necessary to comply with an effective Commission order, BellSouth will provide <<customer_name>> with the ability to concentrate its sub-loops onto multiple DS1s back to the BellSouth Central Office. The DS1s will then be terminated into <<customer_name>>’s collocation space. TR-008 and TR303 interface standards are available.

  • Installation Services 3.1 The Bitstream 2a Service includes a Standard Install as set out below (in each case to the extent that the relevant provisioning works are not already complete for the relevant Service Order).1

Time is Money Join Law Insider Premium to draft better contracts faster.