Distributed architecture Sample Clauses

Distributed architecture. A sample is selected in a biobank to be shared in BIOPOOL with a software application.  This software processes the sample and the pyramidal structure of images is generated and sent from the biobank to the Centralised Index of Images.  This software informs to a module the image search engine about a new sample arrival and the descriptors of the image are extracted and sent to the image search engine.  This software informs to a module of the text search engine about a new sample arrival and the descriptors of the clinical data are extracted and sent to the text search engine.  The pyramidal structure of images is stored in the Centralised Index of Images.  The thumbnail image of a sample is stored in the Centralised Index of Images.
Sample 1
AutoNDA by SimpleDocs
Distributed architecture. The objective of the evacuation route guidance architecture (ERGA) is to provide individualized route guidance to evacuees over an app on their smartphones based on the evacuation information received from connected smartphones within the building and the building sensor network. However, even if an evacuee did not have a smartphone available, s/he could still receive information on relevant evacuation directions, e.g., through LED displays on the walls of a smart building. ERGA (Figure 8) consists of user agents (UA) and a network of smart building (SB) agents.
Sample 1
Distributed architecture. Dealing with real-time and near real-time systems, where several entities are in- volved, each one either producing or consuming data, is naturally achieved by means of a distributed environment. This means that those several entities could be located not only on different systems, but also in different geographical areas. Of course, such kind of an environment requires that the different systems must communicate each other in order to coordinate the management of computation tasks, increasing the complexity of its construction and setup. On the other hand, several advantages can be listed:  Fault-tolerance. Replicating the main roles of the architecture among different systems makes easy to avoid stops of the architecture after a failure (either hardware or software one). In this way the availability of the system is in- creased, while the overhead of maintaining consistency among replicas should be taken into account when, for example, they stores data.  Scalability. When the number of users or messages increases, the load of the entire architecture increases. This leads to higher latencies and possible mes- sage losses, not always admitted by applications. A distributed environment is more suitable for dealing with this increase of load, by means of, for example, adding a new node to the architecture and route some requests to it.  Performance. Having more replicas allows load distribution among them, even- tually reducing the service time for a single request, since the workload is gen- erally maintained as balanced as possible among all nodes. Furthermore, from a user point of view, a distributed architecture allows clients to in- tegrate their modules with the whole system, while keeping them at their premises, and hence maintaining the full control on them.
Sample 1
Distributed architecture. Dealing with real-time and near real-time systems, where several entities are in- volved, each one either producing or consuming data, is naturally achieved by means of a distributed environment. This means that those several entities could be located not only on different systems, but also in different geographical areas. Of course, such kind of an environment requires that the different systems must communicate each other in order to coordinate the management of computation tasks, increasing the complexity of its construction and setup. On the other hand, several advantages can be listed: • Fault-tolerance. Replicating the main roles of the architecture among different systems makes easy to avoid stops of the architecture after a failure (either hardware or software one). In this way the availability of the system is in- creased, while the overhead of maintaining consistency among replicas should be taken into account when, for example, they stores data.
Sample 1

Related to Distributed architecture

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • 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.

  • Traditional Medicine Cooperation 1. The aims of Traditional Medicine cooperation will be: (a) to build on existing agreements or arrangements already in place for Traditional Medicine cooperation; and (b) to promote information exchanges on Traditional Medicine between the Parties. 2. In pursuit of the objectives in Article 149 (Objectives), the Parties will encourage and facilitate, as appropriate, the following activities, including, but not limited to: (a) encouraging dialogue on Traditional Medicine policies and promotion of respective Traditional Medicine; (b) raising awareness of active effects of Traditional Medicine; (c) encouraging exchange of experience in conservation and restoration of Traditional Medicine; (d) encouraging exchange of experience on management, research and development for Traditional Medicine; (e) encouraging cooperation in the Traditional Medicine education field, mainly through training programs and means of communication; (f) having a consultation mechanism between the Parties' Traditional Medicine authorities; (g) encouraging cooperation in Traditional Medicine therapeutic services and products manufacturing; and (h) encouraging cooperation in research in the fields of Traditional Medicine in order to contribute in efficacy and safety assessments of natural resources and products used in health care.

  • Physical Architecture 59.2.1 CenturyLink's network architecture in any given local exchange area and/or LATA can vary markedly from another local exchange area/LATA. Using one or more of the NIMs herein, the Parties will agree to a physical architecture plan for a specific LATA, or if appropriate based on other requirements in Section 59, Local Calling Area. The physical architecture plan, as described in the Local Interconnection POI Profile, will be discussed during joint implementation planning. CLEC and CenturyLink agree to Interconnect their networks through existing and/or new Interconnection Facilities between CLEC switch(es) and CenturyLink's End Office Switch(es) and/or Tandem Switch(es). The physical architecture plan will be in accordance with Forecasting and Planning requirements in Article IV.

  • Project Team Cooperation Partnering 1.1.3 Constitutional Principles Applicable to State Public Works Projects.

  • ROAD DIMENSIONS Purchaser shall perform road work in accordance with the dimensions shown on the TYPICAL SECTION SHEET and the specifications within this road plan.

  • Programming Phase 2.2.1.2. Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

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