One-on-One sessions

From Tuesday to Thursday, workshop advisors will be available to provide focused support on the specific areas. You will have to sign up at the registration desk, and according to advisor and participants' availability a meeting will be held.

Paul Harrison (Astrogrid)

The AstroGrid common execution architecture (CEA, see talks, overview, more details) provides an interface between the UI, with a few variable parameters, and any command line script, such as a configurable program (e.g. SExtractor) or a pipeline wrapper (e.g. the parseltongue Python AIPS wrapper). The user interface can be dialogue boxes, or a script running in the Astrogrid ACR . The CEA manages the request and the response, which would typically be a VOTable containing the URLs of the images of other data requested and their description using VO standards (e.g. to allow interpretation by tools which understand Simple Image Access). See here for pre-release CEA server details

Kevin Benson (Astrogrid)

Help set up Registries (if needed) for providers to install to allow them to publish their data

Help install DSA to allow providers to connect their database for publication to the Registry so that it can accept queries from anywhere in the world. This also allows Cone searches.

Help publish metadata to the Registry once the DALToolkit is operational.

Adapting Existing Software to Publish Data to the VO. Examples could include cut-out or mosaicing services, on-the-fly formation of customised interferometry images or SED construction.

Markus Demleitner (GAVO)

Talk: Building a data center -- lessons learnt at GAVO
A bit more than a year ago, GAVO started setting up a publishing infrastructure at Heidelberg. In this talk, we will discuss some of the issues we faced and the solutions we came up with so far. In doing this, we will also try to shed some light on various components necessary or desirable for VO-enabled and custom services.

1-on-1: Publishing as a Service -- GAVO
The GAVO project provides publishing services for scientists and projects that do not want to bother with setting up a VO infrastructure themselves. During the workshop, we will offer one-on-one sessions of typically half a day, going from ingestion to custom services for user-provided data.

Andreas Wicenec (ESO)

ALMA will eventually produce about 0.5 Terabyte of intrferometric datasets per day. These datasets are collected in a quite complex data model consisting of 50+ tables containing the raw visibility data as well as all required calibration and auxillary data. Most of these data are sampled at high temporal frequencies and are still quite far away from the standard product: a 3D image cube with up to 30,000 spectral layers. The ALMA archive data handling system is designed to support on-the-fly and batch processing in order to deliver the data with the latest available calibration applied. Describing ALMA data in the framework of the current VO characterization model is not adequate and thus we are working on extending the model and make it more suitable for this kind of data as well.

Jean-Christophe Malapert (ESO)

1.5 million of frames are currently available through ESO SIA/SSA services. The classical search engines for selecting data through these services are based on both trigonometrical equations and frame centers. At ESO, we created an intersection algorithm based on vectors to take into account the frame footprint in the selection process. In this talk, I will show you the library handling data selection at ESO.
Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r10 - 24 Jun 2008 - PaulHarrison
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback