Technical Presentations Sample Clauses

Technical Presentations. The following presentations were made on current paleoseismic research and related activities in Utah: • Paleoseismicity of the Salt Lake City segment―Results from the Penrose Drive trench investigation; Chris DuRoss, UGS • Update on fault trenching at the Baileys Lake site, West Valley fault zone; Mike Hylland, UGS • Searching for evidence of seismic events in lacustrine sediments in Utah Lake; Quincy Nickens, Brigham Young University • Hurricane Cliffs hydropower and Lake Powell pipeline preliminary Quaternary fault investigation; Dean Ostenaa, Fugro, Inc. • Blue Castle licensing project; Dean Ostenaa, Fugro, Inc. • Summary of preliminary investigations of the Paunsaugunt fault, Utah; Bob Kirkham, RJH Consultants (no Power Point, hard copy handout) • Utah Geological Survey Nephi segment trenching project, June 2012: Chris DuRoss, UGS • Characterizing the central Wasatch fault zone for the Working Group on Utah Earthquake Probabilities; Chris DuRoss, UGS • Comparison of moment rates from GPS observations and late Quaternary earthquakes on the Wasatch fault, Utah; Christine Puskas, UNAVCO • The Working Group on Utah Earthquake Probabilities (WGUEP)―Background, goals, and progress; Ivan Wong, URS Corporation • Basin and Range Province Earthquake Working Group II; Bill Lund, UGS • East Cache fault zone study; discussion leader Bill Lund, UGS A long-standing question exists regarding the status of the National Earthquake Hazard Reduction Program (NEHRP)-funded investigation titled Earthquake Timing on the Southern Segment of the East Cache Fault Zone, Utah by Utah State University (USU). Originally approved by NEHRP in 2007 as a one-year investigation, results of the study are not yet available to the public. Cache Valley is one of Utah’s most populous regions off the Wasatch Front, and as such, the results of the USU investigation are important to seismic-hazard reduction for that area.
Sample 1See All (4)
AutoNDA by SimpleDocs
Technical Presentations. ▪ Canada and Newfoundland and Labrador Aqua Link (CANAL) Presentation - CANAL was first developed as a pilot project through ResEau funding - It was developed as a tool to bring water quality data/information to Canadians - Its main goal is to convert information to knowledge - It is an innovative product that was achieved through partnership under the Agreement - There was a substantial exchange of expertise that allowed this project to work - The general public accesses CANAL through one web page, however, it is blended from federal and provincial xxxxxx - CANAL has also been repackaged and can be accessed through Google Earth - It is an ideal location to continue to add data /tools - CANAL web site is launched and is awaiting a press release under the Agreement - There was a lot of background work to develop CANAL (ie; convert Site Doc into database; convert spreadsheets into database; develop development pressures calculator; development and implementation of WQI protocols with VMV codes; etc.) - The weakest link with CANAL is the downloading of data from ENVIRODAT; it is not user-friendly and the data is out-of-date; it is not being updated and managed properly. - There was a lot of work initiated throughout the CANAL project, however, some of the work never got implemented into the web site (i.e. created an automated calculator but did not implement it; watershed rollup capacity of WQI scores not implemented; site-specific guidelines WQI calculator was developed but not implemented; etc) - NL continued to work in many areas as a result of CANAL (CANAL paper submitted in Dec 2005 awaiting a response; paper on relative ranking of WQMA sites using WQI submitted in Dec 2005 awaiting a response; integration of CANAL into GIS Intranet system) - There is a lot of work continuing that can be incorporated into the CANAL web site such as:
Sample 1Sample 2
Technical Presentations. List of all technical presentations (in reverse chronological order) related to micro-ROS as input for the corresponding achieved KPI in Section 3.6 2020 December, 16th micro-ROS: bringing ROS 2 to MCUs ROS-Industrial Conference 2020 Xxxxxxxxx Xxxxxxxxxxx, Xxxxx Xxxxxxx Xxxxxxx December, 16th Advanced Execution Management in ROS 2 ROS-Industrial Conference 2020 Xxxxx Xxxxx November, 12th micro-ROS: bringing ROS 2 to MCUs ROS World 2020 Xxxxxxxxx Xxxxxxxxxxx November, 12th Powered by FIWARE Systems for Robotics-based Agile Manufacturing ROS World 2020 Xxxxxxxxx Xxxxxxxx November, 11th Powered by FIWARE Systems for Agile Production ROS Embedded Working Group Xxxxxxxxx Xxxxxxxx October, 26th Powered by FIWARE Digital Twins for ROS, micro-ROS and OPC UA based robotics systems Joint FIWARE and ETSI ISG CIM Workshop on Digital Twins Xxxxxxxxx Xxxxxxxx September , 23rd FIWARE & micro-ROS "Enabling Robotics Systems on Micro-controllers" FIWARE Wednesday Webinars Xxxxxxxxx Xxxxxxxx September , 20th The rclc Executor: Domain-specific deterministic scheduling EMSOFT 2020 Xxx Xxxxxxxxxx mechanisms for ROS applications on microcontrollers September , 17th micro-ROS: Bringing ROS 2 into microcontrollers ROS 2 TSC Xxxxxxxxx Xxxxxxxxxxx September , 16th micro-ROS benchmarking ROS2 Embedded WG #2 Xxxxxxxxx Xxxxx September , 1st micro-ROS: Bringing ROS 2 into microcontrollers ROS Real-Time Working Group Xxxxxxxxx Xxxxxxxxxxx July, 22nd FIWARE Interfaces with Machine and Robots FIWARE Wednesday Webinar Xxxxxxxxx Xxxxxxxx July, 16th The micro-ROS tutorial at BOSCH BOSCH internal Workshop Xxxxx Xxxxxxx Xxxxxxx, Xxxx Xxxxxxx Moral Xxxxxx, Xxxxxxxxx Xxxxxxxxxxx, Xxxxx Xxxxx, Xxx Xxxxxxxxxx July, 7th Bringing micro-ROS to PX4-based flying systems PX4 Developers Summit Xxxxx Xxxxxx June, 27th Introduction to micro-ROS: getting started with Zephyr ROS Developers Day Xxxxx Xxxxxxx Xxxxxxx Xxxx, 25th Micro XRCE-DDS & micro-ROS - Bringing DDS and ROS into microcontrollers DIH² Webinar Xxxxxxxxx Xxxxxxxxxxx June, 22th Micro XRCE-DDS & micro-ROS - Bringing DDS and ROS into microcontrollers FIWARE TSC Xxxxxxxxx Xxxxxxxxxxx June, 17th Micro XRCE-DDS & micro-ROS - Bringing DDS and ROS into microcontrollers FIWARE Foundation webinar Xxxxxxxxx Xxxxxxxxxxx June, 12th Micro XRCE-DDS & micro-ROS - Bringing DDS and ROS into microcontrollers FIWARE Robotics Tech Roadmap WG Xxxxxxxxx Xxxxxxxxxxx March, 4th OFERA Workshop on Overcoming Xxxxx Xxxxx the boundaries of today's Robotics Software Enginee...
Sample 1
Technical Presentations. 3.2.1. Integrated sustainable solid waste management in Ghana- Challenges and prospects 3.2.2. Integrated sustainable solid waste management in Ghana- Socioeconomic constraints and prospects 3.2.3. Integrated solid waste management- Institutional and legal challenges
Sample 1
Technical Presentations. The following presentations were made on current paleoseismic research and related activities in Utah: • Brigham City segment, trenching update; Tony Crone/Steve Personius, USGS • Washington fault northern segment, trenching update; Bill Lund/Tyler Knudsen, UGS • Washington fault Southern Beltway trenching investigation; Dave Simon, Simon - Bymaster, Inc. • U.S. Bureau of Reclamation Utah fault studies update; Larry Anderson, USBR • Bear River fault zone, trenching update; Suzanne Hecker, USGS • Salt Lake City segment/West Valley fault zone investigation, progress report: Mike Hylland, UGS • Working Group on Utah Earthquake Probabilities; Ivan Wong, URS Corp. A scheduled presentation by Jim Evans, USU, on the East Cache fault zone trenching study was cancelled because Jim did not attend the meeting.
Sample 1
Technical Presentations. Xxxx Xxxxxxxxxxx from DTU summarized the conclusions drawn during the Symposium and listed the many topics tackling blade erosion. He highlighted the typical challenges and indicated the five work directions that were identified. He concluded by answering the question “What can we learn from modelling?” and presented the main directions and their outputs. The most promising ones are structured coatings, AI & data management and the inclusion of manufacturing defects in models. Xxxxxxx Xxxx from ORE Catapult presented a research plan including industry needs: lifetime prediction and material solutions. She highlighted the role of recovery and stressed the need to understand real damage types and to standardize data analysis. The main challenge is to make rain erosion tests as close to reality as possible. Xxxxxxx Xxxxxxxxx from SGRE described how the failure modes caused by rotating arm rain erosion tests, with realistic speeds but accelerated rain, correlate well with field data (DuraLedge project). He presented state of the art modelling and mentioned further research needs towards understanding the governing parameters of blade erosion. According to him, the Cobra project represents a good starting point. Finally, he presented the existing leading- edge protection (LEP) types and research needs in this area as well, which lie mainly in the need for standardization within the industry. Xxxxxxxx Xxxxxxx from University Cardenal Herrera – CEU started on presenting current results of his research on material properties and modelling; he tackled the erosion problem as an acoustic problem, investigating stress transmission through the different layers of a rigid body (blade model). This approach allows to decomplexify the model, and separates fatigue in two distinct categories: wear and delamination. Internal defects (bubbles) and their damping effect on the strain in LEP multilayer systems especially raised the interest of the audience. Xxxx X Xxxxx from Xxxxxxx University provided an overview and assessment of use of the Weather Research and Forecasting (WRF) tool to estimate the leading-edge erosion (XXX) potential of a given location for current and future conditions. Results of simulations for the USA showed that, in regions prone to hail events, a curtailment of the turbine for 95 minutes per year could reduce the energy transfer from the environment to the blade by 96%! Forecasting these events could therefore contribute greatly to erosion mitigation. T...
Sample 1

Related to Technical Presentations

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Technology Research Analyst Job# 1810 General Characteristics

  • Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • TECHNICAL EVALUATION (a) Detailed technical evaluation shall be carried out by Purchase Committee pursuant to conditions in the tender document to determine the substantial responsiveness of each tender. For this clause, the substantially responsive bid is one that conforms to all the eligibility and terms and condition of the tender without any material deviation. The Institute’s determination of bid’s responsiveness is to be based on the contents of the bid itself without recourse to extrinsic evidence. The Institute shall evaluate the technical bids also to determine whether they are complete, whether required sureties have been furnished, whether the documents have been properly signed and whether the bids are in order. (b) The technical evaluation committee may call the responsive bidders for discussion or presentation to facilitate and assess their understanding of the scope of work and its execution. However, the committee shall have sole discretion to call for discussion / presentation. (c) Financial bids of only those bidders who qualify the technical criteria will be opened provided all other requirements are fulfilled. (d) AIIMS Jodhpur shall have right to accept or reject any or all tenders without assigning any reasons thereof.

  • Technical Specifications and Drawings a) The Goods and Related Services supplied under this Contract shall conform to the technical specifications and standards mentioned in Section VI, Schedule of Requirements and, when no applicable standard is mentioned, the standard shall be equivalent or superior to the official standards whose application is appropriate to the Goods' country of origin. b) The Supplier shall be entitled to disclaim responsibility for any design, data, drawing, specification or other document, or any modification thereof provided or designed by or on behalf of the Procuring Entity, by giving a notice of such disclaimer to the Procuring Entity. c) Wherever references are made in the Contract to codes and standards in accordance with which it shall be executed, the edition or the revised version of such codes and standards shall be those specified in the Schedule of Requirements. During Contract execution, any changes in any such codes and standards shall be applied only after approval by the Procuring Entity and shall be treated in accordance with GCC Clause 33.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.

  • Research Reports Distributor acknowledges that Dealer may prepare research reports relating to the Fund that are not to be used for marketing purposes (“Research Reports”). Distributor hereby authorizes Dealer to use the name of the Fund, Distributor and BREDS in Research Reports.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!