1 / 5

AVM and Chandra: An Update on Lessons Learned

AVM and Chandra: An Update on Lessons Learned. Joe DePasquale & Kim Arcand. Chandra Images & Metadata. Since 2008, all Chandra release .tiff images, past & present, have contained AVM metadata.

aquene
Download Presentation

AVM and Chandra: An Update on Lessons Learned

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. AVM and Chandra: An Update on Lessons Learned Joe DePasquale & Kim Arcand

  2. Chandra Images & Metadata • Since 2008, all Chandra release .tiff images, past & present, have contained AVM metadata. • Lesson learned: Simple enough to do by hand with a template, but better to do dynamically through the web database. • Chandra web team ported a web version of VAMP's online AVM tool which dynamically connects to Chandra's database and loads the necessary information into an AVM ready file in XMP format.

  3. Numerous uses for the tagged image files: Chandra Images & Metadata • Flickr Commons • http://www.flickr.com/ • SI Photography Initiative • http://photography.si.edu/ • WorldWide Telescope • http://worldwidetelescope.org/ • Sky in Google Earth • http://earth.google.com/ • Google Sky • http://www.google.com/sky/ • Wikisky • http://www.wikisky.org/ • Digital Planetariums, etc • Lesson learned: If you do something useful, people will use it (maybe). And, it helps to have more people power to get “extra projects” done. • Partially dependent on getting the WCS into more images, however, and we hope to push more images into the digital environments, instead of just a handful.

  4. Chandra Images & Metadata • Approximately 35 Chandra images (out of hundreds available) have WCS embedded in them. • Lesson learned: Adding WCS to X-ray data is still cumbersome – but worth it. • Pinpoint WCS: extremely versatile and easy to use • Astrometry.net: all goes well if FoV > 3 arcmin across with optical data. Layer the optical data in and we get the WCS. If not: Background star fileMatch image with FITS that has similar FoV and WCS information (in progress). Plus Python scripts to use WWT for visual inspection and correction of WCSAVM information.

  5. Chandra Images & Metadata “AVM Explorer” to allow easier WCS matching and AVM editing, all in one program. The WCS matching would be automated where you could drop an image into the left box and a FITS file in the right. Using photometry & source matching, WCS map could be fitted to the image. After dropping in the images you click on the match button and detected sources would be shown for visual inspection. The editor on the right is an easy AVM editor. AVM tools are spread out, and not collected into one easy program for usage. This program, the AVM Explorer would do that. • What’s next? • Debugging of Pinpoint sw & finalization of auto-fill AVM pipeline on Chandra servers. • Tag additional resource files and supplementary images/video • Do more content within the digital environments. • Building python code on top of exempi python module developed by L. Holmes (Python-XMP-Toolkit) for AVM automation. • Automatic AVM workflow through Pinpoint, Astrometry.net, Python-XMP-Toolkit, custom code.

More Related