DESCRIPTION: AutomN is concerned with automating the tedious task of protein interaction pathway discovery using only protein sequences as input. AutomN.

Slides:



Advertisements
Similar presentations
In Silico Primer Design and Simulation for Targeted High Throughput Sequencing I519 – FALL 2010 Adam Thomas, Kanishka Jain, Tulip Nandu.
Advertisements

Advanced SQL Schema Customization & Reporting Presented By: John Dyke As day to day business needs become more complex so does the need for specifically.
Lecture # 2 : Process Models
Key-word Driven Automation Framework Shiva Kumar Soumya Dalvi May 25, 2007.
Bologna Process in terms of EU aims and objectives
T. E. Potok - University of Tennessee Software Engineering Dr. Thomas E. Potok Adjunct Professor UT Research Staff Member ORNL.
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
R Mohammed Wahaj. What is R R is a programming language which is geared towards using a statistical approach and graphics Statisticians and data miners.
Software Engineering COMP 201
Software Evolution Managing the processes of software system change
Agenda Overview Why TransCAD Challenges/tips Initiatives Applications.
Major Application: Finding Homologies (C) Mark Gerstein, Yale University bioinfo.mbb.yale.edu/mbb452a.
MERTIS: Modifiable, Extensible, Real-Time, Interactive Simulation Leandro Basallo ◦ Ryan Leigh ◦ Sam Talaie ◦ Regan Snyder with Dr. Sergiu Dascalu and.
Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Chapter Chapter 7: Expert Systems and Artificial Intelligence Decision Support.
V-FIRE: Virtual Fire In Realistic Environments Michael Penick ◦ Grant Kelly ◦ Juan Quiroz with Dr. Fred Harris, Dr. Sergiu Dascalu, and Brian Westphal.
Abstract The University Class Scheduler (U.C.S) is an innovative scheduling tool. It is intended to be used by major Universities to schedule classes into.
Overview of Software Requirements
Building Knowledge-Driven DSS and Mining Data
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
L ECTURE 2 S OFTWARE P ROCESSES 1. O BJECTIVES To describe outline process models for requirements engineering, software development, testing and evolution.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,
Presented by Brian Griffin On behalf of Manu Goel Mohit Goel Nov 12 th, 2014 Building a dynamic GUI, configurable at runtime by backend tool.
Platforms for Learning in Computer Science July 28, 2005.
ABSTRACT CONCLUSION U iPack: A UNR iPhone Application A.J. Henriques ◦ Christian Maloney ◦ Jeff Naruchtparames Instructor: Dr. Sergiu Dascalu, PhD External.
Team 20 Advisor Dr. John Keenan 2:30 pm – 3:00 pm 3:00 pm – 3:30 pm Abstract Course scheduling is an integral part of the college experience. At the University.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
I. Pribela, M. Ivanović Neum, Content Automated assessment Testovid system Test generator Module generators Conclusion.
Testing. Definition From the dictionary- the means by which the presence, quality, or genuineness of anything is determined; a means of trial. For software.
“SEMI-AUTOMATED PARALLELISM USING STAR-P " “SEMI-AUTOMATED PARALLELISM USING STAR-P " Dana Schaa 1, David Kaeli 1 and Alan Edelman 2 2 Interactive Supercomputing.
Extended Prelude to Programming Concepts & Design, 3/e by Stewart Venit and Elizabeth Drake Chapter 2: Developing a Program.
UPC/SHMEM PAT High-level Design v.1.1 Hung-Hsun Su UPC Group, HCS lab 6/21/2005.
A Spring 2005 CS 426 Senior Project By Group 15 John Studebaker, Justin Gerthoffer, David Colborne CSE Dept., University of Nevada, Reno Advisors (CSE.
CS 325: Software Engineering March 17, 2015 Applying Patterns (Part A) The Façade Pattern The Adapter Pattern Interfaces & Implementations The Strategy.
AUTOMATION OF WEB-FORM CREATION - KINNERA ANGADI – MS FINAL DEFENSE GUIDANCE BY – DR. DANIEL ANDRESEN.
3DCS Advanced Analyzer/Optimizer Module © Dimensional Control Systems Inc DCS Advanced Analyzer/Optimizer Equation Based Tolerance Analysis Quick.
Protein Molecule Simulation on the Grid G-USE in ProSim Project Tamas Kiss Joint EGGE and EDGeS Summer School.
Verb Expansion Game Team 3 Bryan Bloss Jeremy Comardelle Gordon Gable Gleyner Garden Sponsored By: Dr. Beth Young.
1 Chapter Nine Using GUI Objects and the Visual Studio IDE.
Systems Analysis and Design in a Changing World, Fourth Edition
Cheap N Fast Web Service Sandeep Anantharaman Mahim Lakhani.
1 CMPT 275 High Level Design Phase Modularization.
ES component and structure Dr. Ahmed Elfaig The production system or rule-based system has three main component and subcomponents shown in Figure 1. 1.Knowledge.
Creating Macros in Excel Adding Automated Functionality to Excel & Office Applications.
1 CSCD 326 Data Structures I Software Design. 2 The Software Life Cycle 1. Specification 2. Design 3. Risk Analysis 4. Verification 5. Coding 6. Testing.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
In the Labs… X-Bot 2003 by Overtech Technologies.
INTRODUCTION GORT is a virtual 3D modeling environment for computer programmers. Its main area of focus is to aid in the education of programmers learning.
Theme 2: Data & Models One of the central processes of science is the interplay between models and data Data informs model generation and selection Models.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
An Introduction to Forms. The Major Steps of a MicroSoft Access Database  Tables  Queries  Forms  Macros  Reports  Modules On our road map, we are.
August 2003 At A Glance The IRC is a platform independent, extensible, and adaptive framework that provides robust, interactive, and distributed control.
D R A T D R A T ABSTRACT Every semester each department at Iowa State University has to assign its faculty members and teaching assistants (TAs) to the.
May08-21 Model-Based Software Development Kevin Korslund Daniel De Graaf Cory Kleinheksel Benjamin Miller Client – Rockwell Collins Faculty Advisor – Dr.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Chapter – 8 Software Tools.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
Procedural programming Procedural programming is where you specify the steps required. You do this by making the program in steps. Procedural programming.
QC – User Interface QUALITY CENTER. QC – Testing Process QC testing process includes four phases: Specifying Requirements Specifying Requirements Planning.
Zach Miller Computer Sciences Department University of Wisconsin-Madison Supporting the Computation Needs.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
1 Process activities. 2 Software specification Software design and implementation Software validation Software evolution.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 13 Computer Programs and Programming Languages.
Advanced Computer Systems
GUI Design and Coding PPT By :Dr. R. Mall.
System Design Ashima Wadhwa.
APPLICATIONS OF BIOINFORMATICS IN DRUG DISCOVERY
Learning to Program in Python
From Use Cases to Implementation
Presentation transcript:

DESCRIPTION: AutomN is concerned with automating the tedious task of protein interaction pathway discovery using only protein sequences as input. AutomN wraps many bioinformatics tools into one easy to use, streamlined package. AutomN is entirely GUI-based, making it so that the user can immediately point and click to select the options they want instead of having to consult long manuals in order to find a specific command line switch they desire. AutomN uses a pipeline architecture, meaning that bioinformatics analysis tools are called one after another on a set of data, continually transforming it until the desired result is achieved. AutomN takes two protein sequences as input and attempts to locate a structure for each sequence using BLAST. If no structure is found, the structure is predicted using Rosetta. Once the structure is defined for both input proteins, they are docked together using ZDOCK. The optimal predictions from the ZDOCK run are then displayed to the user in a graphical format so he or she can decide which interactions are worth further study. ABSTRACT: One of the goals of the structural bioinformatics field is to discover how a protein's sequence determines its structure and how these protein structures interact with each other. A plethora of tools that tackle specific areas of this problem have been developed and focus primarily on protein docking, homology modeling and threading, structure prediction, and similarity comparison. Unfortunately, the use of several of these non-intuitive and user un-friendly tools are required for the simplest research project. The learning curve of these tools and repetitious tasks required to operate them consume massive quantities of researcher time. AutomN seeks to eliminate this by automatically wrapping many of these tools in an easy to use GUI and automating the entire process. Figure 2 CONCLUSION: AutomN is a new bioinformatics tool that uses a pipeline architecture to automate the process of converting two protein sequences into an ensemble of probable docked protein complexes. By understanding which proteins interact with others, it becomes possible to modify these interactions with newly created drugs and to better understand the inner workings of all organisms. The AutomN team hopes to increase throughput of any research-oriented organization and broaden the user base of sophisticated research tools. In addition, AutomN is so easy to use that almost any student can utilize it, making it a candidate as a learning tool. The main goals of this tool are to save time by automating repetitive research tasks and to allow users with limited knowledge of modeling techniques to accomplish quite complex tasks. For our first version, AutomN does not implement any new bioinformatics algorithms, but focuses on making existing algorithms easier to use. AutomN has great potential in the research and learning community. Hopefully with a few years of continued work, AutomN will become commonplace in the arsenal of widely available bioinformatics tools. FUTURE WORK: For subsequent versions, our focus will be directed toward allowing AutomN to utilize any bioinformatics algorithm in our problem domain. This adaptable plug-in architecture ensures the user is not tied to a particular analysis module. Also, AutomN should be able to detect if a module has failed and be able to recover from the error gracefully. Lastly, advanced analysis routines which help the researcher determine the validity of the docked structures will be added. Figure 3 Figure 1: AutomN’s Graphical User Interface Figure 2: Data Flow through the AutomN Pipeline Figure 3: AutomN generated docked structure of PDB 1A15 and 1CRN Note: AutomN is a play on the words autumn and automatic. Figure 1 This project was developed in Spring 2005 as part of the course CS 426 Senior Projects Advisors: Dr. Brian W. Beck 1, Dr. Sergiu Dascalu 2, and Brian Westphal 2 Department of Biochemistry 1, CSE Department 2, UNR