1 / 18

VLAB Framework (afternoon)

VLAB Framework (afternoon). Gordon Erlebacher. Principal IT Investigators. University of Minnesota Prof. David A. Yuen : Dept. of Geology and Geophysics Martin D. Lyness Prof. Renata Wentzocvitch : Dept. of Chemical Engineering and Materials Science Dr. Cesar da Silva Pedro da Silveira

eavan
Download Presentation

VLAB Framework (afternoon)

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. VLAB Framework (afternoon) Gordon Erlebacher

  2. Principal IT Investigators • University of Minnesota • Prof. David A. Yuen : Dept. of Geology and Geophysics • Martin D. Lyness • Prof. Renata Wentzocvitch : Dept. of Chemical Engineering and Materials Science • Dr. Cesar da Silva • Pedro da Silveira • Florida State University • Prof. Gordon Erlebacher : School of Computational Science • Evan F. Bollig • Indiana University • Dr. Marlon Pierce : IU Community Grids Lab

  3. Student Internships • Ana Sallstrom (UMN): Workflow Visualization • Javier Roman (UMN): Making Vlab Secure • Frank Lyness (UMN): Remote Visualization, Ajax • Mike Nielson (UMN): Managing Vlab resources using J2EE • Dan Rao (UMN): Potential Repository • Laurie Labadie (FSU): Interactive Data Mining of Workflows • Celine Gestas (FSU): Lineplot Visualization

  4. WATT: An OverviewOn the Web:http://www.gorerle.com/vlab-wiki/index.php?title=WATT • The Web Automation and Translation Toolkit (WATT) • Automates the conversion of software, specifically for the internet. • Translates source code to incorporate new technologies. • Translator was written in Ocaml language • Currently supports direct compilation of VTK (http://www.vtk.org) Tcl scripts into remote visualization web services. • Watt-live • http://vlab2.scs.fsu.edu/watt-live/

  5. WATT : Design • Tcl scripts written for VTK are sent to our Watt Compiler • WATT generates C++ calls for VTK and adds template calls to gSOAP (http://www.cs.fsu.edu/~engelen/soap.html) • gSOAP headers autogenerated by WATT are compiled by the soapcpp2 compiler to produce SOAP enabled C++ objects • WATT output plus additional gSOAP output are compiled together to produce a single binary visualization web service

  6. Watt: next steps • Restructure Watt to avoid translation from Tcl to C++ (time consuming) • Automatically generate graphical user interfaces: proc AddContours { numContours rangeMin rangeMax } { #WATT_GUI_SETVALUE "Generate Contours" "# of contours" "min" "max”….

  7. Portlet Interfaces :: Overview • Using Gridsphere 2.1 portlet container and grid libraries (http://www.gridsphere.org) • JSR 168 standard portlets • VLab PWscf Portlets • Already submitted and completed jobs • Project input revisions • Status and advanced submission monitoring • Visualization Clients • Pseudo-Potential Repository

  8. Project Manager Portlets The Project manager (left two portlets) is integrated into many portal tabs to show the user his/her current project status and an overview of all projects maintained by the portal. The input portlets (right) walk you through entering important calculation information about the project.

  9. Advanced Monitoring Job monitor tracks progress of project submission Detailed view allows for advanced manipulations within each workflow step

  10. Charge Density Visualizations • Uses multiple technologies: Java Servlet, gSOAP Web Service, JSR 168 Portlet, AJAX, CSS2, & JSP • Generates visualizations using WATT generated web services • Interacts dynamically with the visualization service using Java Reflection libraries within a Servlet which is accessed via AJAX within the Gridsphere portlet interface.

  11. Pseudo-Potential Repository Access to multiple databases Create/delete/edit atoms, pseudo potentials and exchange-correlation functionså

  12. Workflow Visualization Applet

  13. Getting it online(simplifed workflow view) • What’s left? • Reading in projects from the job monitor • Rearranging the tree to make reading tasks easier • Working on it!

  14. Thermodynamic Visualization • Built as a WebStart application based on VisAd • Takes output from Phonon code and allows user to plot the data in one or multiple output files

  15. Future Perspectives • Investigating Ruby on Rails framework as a viable development platform. • Highly abstracted for rapid development • Enhanced Interface design using various CSS & AJAX techniques • JavaScript 3D for inline browser remote visualization trackball style manipulations • Expanding Services: • Dynamic workflow generation • Improved Visualization Services

  16. Next steps • Seek some physicists with no knowledge of the portal system who would be willing to try it out and provide feedback • We’d like to sollicit feedback for a fixed time period before prioritizing issues and addressing them

  17. VLab Activities On the web:http://vlab.msi.umn.edu/events/ • Workshops & Seminars • Second VLab Workshop - will take place at the University of Minnesota Walter Library Room 402, August 5-10, 2007. • http://vlab.msi.umn.edu/events/secondworkshop.shtml • Tutorials • No currently scheduled events. • Summer Research Internship (Univ. of Minnesota) • Undergraduate students, each from unique educational disciplines actively participate in research and development of novel technologies for VLab. • Nuggets: Short Research Bulletins • Straight to the point updates as we accomplish new goals • http://vlab.msi.umn.edu/reports/nuggets/

  18. The WATT Compiler • Uses type-inference to convert typeless Tcl to strictly-typed C++ • Compiler is language independent; configuration modules define input and output syntax. • Register and Interrupt systems allow the compiler to reconfigure itself as it runs. • Parser for input configuration files registers new types or translations that are immediately available for use. • Interrupts are invoked by registered inputs and result in unique output (i.e. Tcl “set a 1” --> C++ “int a = 1;”)

More Related