28,291 research outputs found

    Web-Based Visualization of Very Large Scientific Astronomy Imagery

    Full text link
    Visualizing and navigating through large astronomy images from a remote location with current astronomy display tools can be a frustrating experience in terms of speed and ergonomics, especially on mobile devices. In this paper, we present a high performance, versatile and robust client-server system for remote visualization and analysis of extremely large scientific images. Applications of this work include survey image quality control, interactive data query and exploration, citizen science, as well as public outreach. The proposed software is entirely open source and is designed to be generic and applicable to a variety of datasets. It provides access to floating point data at terabyte scales, with the ability to precisely adjust image settings in real-time. The proposed clients are light-weight, platform-independent web applications built on standard HTML5 web technologies and compatible with both touch and mouse-based devices. We put the system to the test and assess the performance of the system and show that a single server can comfortably handle more than a hundred simultaneous users accessing full precision 32 bit astronomy data.Comment: Published in Astronomy & Computing. IIPImage server available from http://iipimage.sourceforge.net . Visiomatic code and demos available from http://www.visiomatic.org

    Location based mobile computing - a tuplespace perspective

    Get PDF
    This is the post-print version of the Article. The official published version can be accessed from the link below - Copyright @ 2006 IOS PressLocation based or "context aware" computing is becoming increasingly recognized as a vital part of a mobile computing environment. As a consequence, the need for location-management middleware is widely recognized and actively researched. Location-management is frequently offered to the application through a "location API" (e.g. JSR 179) where the mobile unit can find out its own location as coordinates or as "building, floor, room" values. It is then up to the application to map the coordinates into a set of localized variables, e.g. direction to the nearest bookshop or the local timezone. It is the opinion of the authors that a localization API should be more transparent and more integrated: The localized values should be handed to the application directly, and the API for doing so should be the same as the general storage mechanisms. Our proposed middleware for location and context management is built on top of Mobispace. Mobispace is a distributed tuplespace made for mobile units (J2me) where replication between local replicas takes place with a central server (over GPRS) or with other mobile units (using Bluetooth). Since a Bluetooth connection indicates physical proximity to another node, a set of stationary nodes may distribute locality information over Bluetooth connections, and this information may be retrieved through the ordinary tuplespace API. Besides the integration with the general framework for communication and coordination the middleware offers straightforward answers to questions like: Where is node X located? Which nodes are near me? What is the trace of node Y
    corecore