70 likes | 227 Views
Tribe = ViRBO. HP VxO Gathering of the Tribes: pre-VOiG Meeting for the Virtual Heliophysics Great Observatory (HGO). Bob Weigel 11 June 2007 Denver, Colorado. People Involved. PI * Bob Weigel (George Mason University) Data * Dan Baker (CU/LASP, Data and metadata)
E N D
Tribe = ViRBO HP VxO Gathering of the Tribes:pre-VOiG Meeting for the VirtualHeliophysics Great Observatory (HGO) Bob Weigel 11 June 2007 Denver, Colorado
People Involved PI * Bob Weigel (George Mason University) Data * Dan Baker (CU/LASP, Data and metadata) * Sebastian Boudier (Onera, Data calibration) * Janet Green (NOAA/SEC, Data and metadata) * Shri Kanekal (CU/LASP, Data and metadata) * Reiner Friedel (LANL, Data and calibration) * Paul O'Brien (Aerospace, Data and metadata) Software * Eric Kihn (NOAA/NGDC, ViRBO Web and API) * Mikhail Zhizhin (RFO, ViRBO Web and API) * Jeremy Faden (Cottage Systems, ViRBO Software)
Brief reminder of science • How are particles accelerated and lost? • Instrument data • Reanalysis • Calibration • Prediction • Simulation
Status of implementation • Our first major public release will not be until the Fall AGU • Our development efforts will be kept as public as possible (through wiki, http://virbo.org/wiki). Code, information, and metadata is added to this page as I get it. • Familiar enough with SPASE and Metadata requirements to start assigning tasks to scientists (prior to ViRBO All-Hands meeting the week of July 23) • 25% of data in archaic forms converted to CDF • Tested a number of server technologies. Settled on DODS/THREDDS. Integrated this into VxOware codebase • Plotting software is 80% feature complete. Metadata reading and interpreting software is in the process of being developed (hold-up is the completion of Metadata records) • VxOware2LiveCD is in development this summer. Goal is for a developer to boot, inject some of their own data, and evaluate if it is a project they want to build upon or use • Primary effort for this summer and fall is to prepare metadata and put 100% of data into CDF so that it is available from DODS server
Metrics • Audience: Initially RB Scientists. Eventually, I want to target people interested in real-time data • Expected use: • Initially a “portal” for radiation belt scientists. This is why I think it is important to have a page that states what data that may be of interest to them that is not available through ViRBO. • A set of software for building a VxO. • Feedback; what is success? At least 1 “independent” submission of a data set. That is, someone who I don’t know well says, without prompting, “can I use ViRBO to store my data set and communicate it with the community”. Continued requests to be on proposals (three so far).
Status of inter-VxO collaborations • How we have collaborated • With VMO on who will deal with what • What we have to offer • Eventually VxOware, but I only expect pieces of this to be of interest to this group (epscially the plotting functionality and SPASE parsing Java code, and possibly our LiveCD scripts) • Where we could use help • CDF backend for DODS/THREDDS • Fix Matlab CDF readers (done) • Make SPASE email list available to public and search engines • Layout and organization of SPASE web page
Fall AGU meeting demonstration • DODS/THREDDS/VxOware/Autoplot access to 80% of our data. • Ability for users to correct “typos” in metadata for such things as powerpoints, software, etc. • Ability for a user to “inject” data • Ability to easily archive a conference that was hosted on MediaWiki. • VxOWare2LiveCD • Shopping Cart features of saving and sharing both data queries and data views generated by VxOware Autoplot.