1 / 6

TASK 6: DEVELOPMENT OF ADVANCED ANALYTICAL FRAMEWORK

TASK 6: DEVELOPMENT OF ADVANCED ANALYTICAL FRAMEWORK. Ricardo Dobry Kickoff Meeting RPI, Nov. 19, 2005. Originally Proposed Timeline and Integration of Tasks. Original Definition of Advanced Analytical Framework (AAF) in Proposal.

eron
Download Presentation

TASK 6: DEVELOPMENT OF ADVANCED ANALYTICAL FRAMEWORK

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TASK 6: DEVELOPMENT OF ADVANCED ANALYTICAL FRAMEWORK Ricardo Dobry Kickoff Meeting RPI, Nov. 19, 2005

  2. Originally Proposed Timeline and Integration of Tasks

  3. Original Definition of Advanced Analytical Framework (AAF) in Proposal • Called Advanced Identification and Analysis Framework in proposal (Task 6b) • Objective: to construct a bridge between FEM analyses, experimental results and DEM simulations • It would involve: • design of optimal sensor configurations • development of advanced analysis and visualization tools merging experimental, DEM and FEM results • Identification of hierarchy of computational models capable of predicting seismic response of soil-pile systems

  4. After going around several weeks, following picture emerged for basic form of AAF: • At RPI-NEES, we are in process of developing metadata software for getting centrifuge testing data into NEES Repository • If Buffalo-NEES could develop consistent metadata software for 1g tests done in our project, then 1g and centrifuge tests in our research would produce consistent results that could be manipulated together. Then DEM and FEM simulations would be requested to convert their results in same form • This metadata software combined with RPI’s 3D data viewer would constitute the basic (starting) form of our AAF • H. Radwan (RPI NEES) and J. Hanley (U. Buffalo-NEES) are working together in metadata software, and Hassan will integrate it with the 3D viewer by March 06. A. Elgamal and M. Zeghal have agreed to convert their FEM and DEM results to corresponding format

  5. More on the AAF (I) • All four sources of results for free field and pile tests will look like “centrifuge test results” to AAF, so results of a given 1g test (say 1A) will be entered 4 times into the system: • 1g test: “Centrifuge test A” • Centrifuge test: “Centrifuge Test B” • FEM prediction: “Centrifuge Test D” • DEM prediction: “Centrifuge Test C” • If foundation system, shaking input and locations of “sensors” are consistent between the four databases, then any software developed for one of these four databases (or to implement comparisons between two or more databases), can be used without change for other databases or combinations of databases. This is because from viewpoint of AAF the four databases look the same

  6. More on the AAF (II) • Basic AAF ready in 3/06; C. Medina takes over AAF in 9/06 • Future issues: • Access, transparency of AAF and AAF-produced results to research team (through NEESit?) • Development of additional software on top of basic AAF (by individual researchers of team that then make software available to rest of team?; centralized software development at RPI as part of Dobrys Tasks 6 or 7?) • Coordination with (and roles of) RPI-NEES and NEESit as part of Dobry’s Tasks 6 and 7

More Related