1. Ellen M. Rathje University of Texas at Austin NEEScomm IT Development Team

2. We’ve got a HUB for that!

3.  Project Warehouse: data repository  Collaborate: group space, wish list  Tools and resources: tools, reports  Simulation: info on simulation

5. Dashboard for your NEEShub activities Your Projects in the Warehouse Your current tools sessions Your contributions to the NEEShub The tools you use most often Your Wishes Your Tickets Your Groups Your Messages

6. Personal Workspace (private) NEEShub Project Warehouse (private/ public) Group Spaces (restricted) There are different levels of sharing and collaboration within NEEShub

8. A centralized data repository for managing, sharing, storing, and publishing research data

9. Descriptions Drawings Mat’l Descriptions Photos Publications Data

10. Every project is created with the same structure This provides consistency between projects and aids in the navigation of project information

11.  Project Experiment Trial Repetition  A project represents an entire research project, which consists of a suite of tests and associated simulations  Each test is set up as an individual experiment  Within each experiment there are several trials or separate events for which data is measured  If the same trial is performed more than once, it may have multiple repetitions The model governing the organization of data within a project

12. NEES-GC: Seismic Risk Mitigation for Port Systems Centrifuge Test of PV Drains Mar 2007 Crane Shake Table Test Nov 2009 Pile-Wharf Connection Test Sept 2007 Sine1Cyclic LoadShake1Shake2 Rep1 Project Experiments Sine2Sine3 Rep1 Repetitions Trials

13. The model governing the organization of data within a project

14. A centralized data repository for managing, sharing, storing, and publishing research data

15.  For each repetition within a trial, there are four data folders that are automatically created 1.Unprocessed data (data collected by Equipment Site)  Raw voltages, channel names, potentially non-standard formats (e.g., binary files) 2.Converted data  Measurement units, instrument names 3.Corrected data  Filtering, baseline corrections, removal of bad data 4.Derived data  Corrected data plus values derived from measured data Remember the data within the Project Warehouse is PUBLIC ASCII files recommended for all sensor data Put all channels into a single ASCII file

16.  Experiment Documentation ◦ Metadata fields within the Project Display ◦ Experimental Setup Report placed in Documentation folder  Sensor Measurement Data ◦ Unprocessed ◦ Converted ◦ Corrected ◦ Derived Data cannot be shared without proper documentation Uploaded by Researcher within 6 months of experiment Uploaded by Site within 1-month of experiment Minimum data requirements: sensor data in engineering units!

17.  The Project Editor ◦ Create, edit, and update projects ◦ File uploads through web interface  The Project Explorer for NEES (PEN) ◦ Efficient upload/download for bulk file management ◦ Direct file upload (not a web interface) ◦ Files organized offline and then uploaded ◦ Recommended for large numbers of files  inDEED Data Viewer ◦ Facilitates browsing/viewing/investigating data within Warehouse without download ◦ Use inDEED data file format https://nees.org/tools/indeed/wiki/CSVFileFormat The nuts and bolts

18. Projects are created using the Project Editor

19. Enhancing bulk upload of files

20. Facilitating data queries

21. Specimen Authoring Tool InDEED

22. Projects with Data Visualization

23.  Definition of Enhanced ◦ Metadata fields in Project Display are complete (including drawings, material properties) ◦ Project includes at least one visualization of data ◦ inDEED is currently the only visualization tool that allows for viewing data within the NEEShub without download Projects with Data Visualization

24. One-stop shop for documentation related to project warehouse

26.  Groups can be: ◦ Public, restricted, or private  Purpose ◦ To facilitate conversation, collaboration, and data sharing between group members ◦ Discussions, wiki posts, and files are in one central location available to all group members ◦ Generate a webpage for your project  Features ◦ Wiki, messaging, discussion boards, and file sharing via the dropbox An easy way to share content and conversation

28.  A group is automatically created for all projects created in the Project Warehouse ◦ Group name has Project in title  Membership is controlled by project team members listed in the Project Editor

29. An easy way to share content and conversation About section can be expanded into a web page for your project

30. An easy way to share content and conversation

33.  SynchroNEES ◦ A graphical user interface for transferring files  Local PC to/from NEES Group workspace  Local PC to/from NEES Personal workspace The nuts and bolts

35.  Contribute tools and resources to share with the community  Submit tickets to get problems/issues resolved  Submit wishes about things you would like to see on the NEEShub  Participate in Usability Study: email e.rathje@mail.utexas.edu to volunteer

37.  Cyberinfrastructure Release Committee (CRC) ◦ Chair: Ellen Rathje (e.rathje@mail.utexas.edu) ◦ Members: JoAnn Browning, Juan Caicedo, Shirley Dyke, Rudi Eigenmann, Tom Hacker, Ayhan Irfanoglu, Santiago Pujol  NEEScomm IT Director ◦ Dawn Weisman (dweisman@purdue.edu)  Data Curator ◦ Standa Pejsa (spejsa@purdue.edu)

38.  Data Upload (January 2012) ◦ Demonstrations of the Project Editor and PEN by graduate students using these tools  High Performance Computing (January 2012) ◦ Demonstrations of accessing Teragrid, OpenScienceGrid for OpenSees and other tools  inDEED /Authoring Tool (February 2012) ◦ Demonstrations of how to generate inDEED visualization files using your data  Getting the most from the hub (March 2012) ◦ Demonstrations of Group Space, Tools, etc