![]() |
|
| Issue 1: March 2008 |
|
| Contributors: Andrew Connolly (University of Washington), Sarah Emery Bunn (Caltech), Mike Fitzpatrick (NOAO), and Roy Williams (Caltech) Editor: Dave De Young (NOAO) |
|
News & Announcements |
|
|
"The National Virtual Observatory: Tools and Techniques for Astronomical Research", has been published as an ASP Conference Series (Volume No. 382) and is available to order at the ASP website. This volume is a collection of the NVO Summer School lectures and tutorials. It includes a complete set of software libraries and worked example
The application form will be available on the summer school website after April 15. Anyone interested in learning how to use the VO for astronomical research is welcome to apply. There will also be sessions for those interested in exposing data through VO protocols. We encourage scientists at any stage of their career, graduate student to tenured professor, to apply. Programming experience in Python or Java is strongly advised. Space and budgetary constraints limit participation to 40 people. Applications will be reviewed by the organizing committee and participants will be informed by July 1, 2008 of their acceptance to the Summer School. There will be a $500 registration fee for participants. If this presents a financial hardship that would preclude attendance, applicants may request a waiver of the fee. The organizing committee will review such requests on a case by case basis. Upon acceptance to the Summer School, the fee will be due by August 1. Accommodations are provided for all participants. In addition, a travel stipend of up to $400 and a per diem stipend of $225 are available for successful applicants from US institutions who can commit to attending the entire course and who do not have funds available to cover these expenses. The NVO Summer School is made possible through the support of the National Science Foundation and the National Aeronautics and Space Administration. Questions about the summer school should be directed to |
|
NVO Inside |
|
|
An emerging theme in the Virtual Observatory is "NVO Inside"—the idea that VO protocols are more prevalent than might be apparent on the surface. Think of the person who says "I don't need NASA satellites to tell me the weather, I just tune into the Weather Channel," with no idea that the data driving that channel comes from those satellites! One way in which NVO has become pervasive is through a format for representing tables, called VOTable. It is based on FITS tables, but has the advantage that it can carry richer metadata: about the data in the table, about the provenance and description of the table. VOTable is scalable to handle bulk data. VOTable is used for catalog data, which is the traditional list of astronomical objects and quantitative attributes; but it is also used in the VO for metadata, or "data about data". When querying a VO service for images or spectra, it is a two-stage process: the response to the query is not the images and spectra themselves, but rather a VOTable describing them, including links to the actual FITS data files. NVO and its international partners have worked with most of the big data centers (HEASARC, IPAC, STScI, CDS, ESO, etc) to make their outputs available in the VOTable format, and they have built tools that visualize and manipulate VOTable. Therefore a teacher or astronomer can now get VOTable from a data center, a query of any of thousands of catalogs with complex constraints, then understand and visualize the results, all with portable, open-source software. Some examples of organizations with NVO Inside are: NED and Simbad: Many services that produce VOTable Is your organization or project NVO Inside? Please let us know! |
|
|
Astronomy has always been one of the most visual of the sciences, but with the growing size of astronomical surveys, how we browse and interact with imagery covering the full sky and at many different wavelengths has become a significant challenge. On August 22nd of last year Google introduced a new feature to Google Earth; Sky in Google Earth (aka Google Sky) that addresses the challenge of exploring Terabytes of imaging data through the use of efficient streaming technologies. Google Sky combines all-sky imagery, common astronomical catalogs, catalog and positional searches, the capacity to annotate images and share these annotations with other users, and the ability to display time domain data (from the motion of the planets to time series of images of variable sources) in a single interface that runs natively on all major platforms. It provides an interactive visualization platform that can be tailored to a wide range of needs from research scientists to amateur astronomers to the public as a whole. To run Google Sky, download the latest Google Earth client from http://earth.google.com and start it up; click the Saturn icon on the top tool bar and the view will switch to the sky overhead. Figure 1 shows the layout of Sky; the left panel displays the default layers that are available as well as any other layers you may have created or downloaded. The search bar above the layers can be used to find objects by name or position on the sky. Clicking on marked objects displays Wikipedia information and links to Google Scholar, ADS, NED, SIMBAD, and other information sources. Documentation on how to use Google Sky can be found here.
While Google Sky provides many different views of the sky, it was designed to be an extensible environment that can both ingest and display a wide range of astronomical data. This means that, from its inception, Sky can be used to upload images and catalogs and share them with other researchers or with the public as a whole. The structure that makes this possible is a markup language used to place objects on the sky. The Keyhole Markup Language (KML) is a standard that references objects to the sky through the use of simple tags Many tools now exist to help users integrate their data with Sky. FITS images with valid coordinates can be easily converted into KML using the open source tool wcs2kml. This program takes in a FITS image, reprojects it to work with Sky, and generates the appropriate KML files. Publishing data with Sky is as simple as running the program and dropping the resulting files in a web accessible directory and notifying your collaborators, or uploading the link to the Google Sky Gallery or to the Google Sky Community. For large images there is an option in wcs2kml to create a pyramid of images at different resolutions, rather than a single image, which saves on network bandwidth requirements. For the command-line averse, staff at STScI have wrapped wcs2kml with a graphical interface which can be downloaded here. There are many more features and ways to work with Google Sky than space permits in this article, and new features and data appear every few weeks in Sky. An example of this is the Google Maps interface to Sky that was released in December. This means that you can embed Sky in any browser and interact with it with all of the capabilities of Javascript, even on an iPhone. Google is interested in feedback on new features, new data or new ways to look at the sky including any mashups you have created for discovering or displaying data on Google Sky; please contact Andrew Connolly (Univ. of Washington/Visiting Faculty at Google) at ajc[at]astro.washington.edu. It is hoped that Sky will provide the VO community with the ability to create, modify and share research and the excitement of research with a very broad community. Happy exploring. |
|
Featured NVO Application |
|
VO-CLI - Command Line Tools for the VO VO-CLI is a package of command-line tools that provides familiar Unix-like access to VO services while hiding much of the complexity of the underlying VO framework from novice users. These tools can be used from the desktop or in scripting environments to build more complex desktop science applications, or for use in back-end CGI scripting to support web applications. Output tables are saved by default as comma-separated values making these easy to import into something like Excel; however, a variety of output table formats may be used (including Google Sky's KML format). A key feature of the package is the ability to use familiar names for both objects and VO resources. A VO resource can be many different things, such as tools, catalogs, or web services. For example, a query for point-source data from 2MASS around NGC4256 will resolve the coordinates of the object automatically and you may refer to the catalog as '2mass-psc'. Most users will quickly learn these familiar resource names after spending a little time browsing the NVO Registry to find the primary resources they'll commonly use, but this name can also be used as a search term to expand a resource list to include, for example, any SDSS service. Two tasks exist to allow the user to experiment with the object and registry search functionality before querying for real data: The VOSESAME task can be used to convert object names to positions so that positions are resolved only once when repeatedly querying for data, and the VOREGISTRY task will allow you to browse the NVO Registry to locate a desired resource, verify the familiar name to use, find a more unique identifier, or simply browse for data services. Searches may be constrained by type of data or the bandpass used, and the search abilities can be used to create data queries that go beyond an astronomer's list of familiar primary resources. The heart of the VO-CLI tasks is VODATA, which combines the other tasks' abilities to create and resolve resource and object lists with the query and retrieval of the actual data. VODATA will automatically parallelize large queries for efficiency, and flags permit the user to create queries for, e.g. "all HST image data" or "X-ray catalog data only". Image data may be accessed directly or downloaded later after a user has selected a desired subset of available data. There is a VO-CLI introductory tour here. This page will lead you through examples of what each of the VO-CLI tools can do and allow you to run the application from the web-page directly. The documentation lists many examples, and with some practice a fairly sophisticated query can be created from the many available options. Figure Caption: Image and catalog overlay of a region around M33 produced using VO-CLI tools to retrieve VO data and local script to render the display. |
|
NVO Calendar |
|
18-21 February , 2008 | Practical Semantic Astronomy Workshop | Pasadena, California 7-11 April | Euro-VO Workshops: Theory in the VO & Grid and the VO | Garching, Germany 19-23 May, 2008 | IVOA Interoperability | Trieste, Italy 3-11 September, 2008 | The 2008 NVO Summer School | Santa Fe, New Mexico 5-8 October 2008 | "Astronomical Data and the Virtual Observatory" session at CODATA21 | Kiev, Ukraine 27-31 October | IVOA Interoperability | Baltimore, Maryland 2-5 November 2008 | ADASS XVIII | Quebec City, Canada |
|
Contact Information: Your feedback is important to us. To make sure we can address your questions and ideas, please send email to Subscription Information: To unsubscribe from news or change your subscription options enter your subscription email address here: http://www.us-vo.org/mailman/listinfo/news Privacy: We respect the privacy of the web and those who use it. For our complete privacy policy, visit http://www.us-vo.org/privacy.cfm |
|