|
|
Workplan for AVO Demo 2005
| No. | Scope of Task | Supervision |
|---|
| T1 | science cases | PaoloPadovani, ST-ECF |
|---|
| T1.1 | collect SWG feedback and input | done |
| T1.2 | definition and selection | done |
| T1.3 | data collections and providers | science team |
| T1.4 | detailed design | science team |
| T1.5 | execution, produce sci. results | science team |
| T1.6 | presentation, dissemination | AVO Exec |
| T2 | SED generation | MarkusDolensky, ESO |
|---|
| T2.1 | data curation | Anita Richards |
| T2.2 | special workflow operators | Mark Allen |
| T2.3 | visualization + analysis | Anita Richards |
| T2.4 | SED support library | Markus Dolensky/Pedro Osuna |
| T3 | data center infrastructure | KeithNoddle, Astrogrid |
|---|
| T3.1 | identify useful middleware components | done |
| T3.2 | workflow builder | Paul Harrison |
| T3.3 | workflow execution and monitoring | Paul Harrison |
| T3.4 | shared storage | Martin Hill |
| T3.5 | data access layer | Martin Hill |
| T3.6 | master registry | Kevin Benson |
| T4 | integration | KeithNoddle, Astrogrid |
|---|
| T4.1 | IVOA compliance | Markus Dolensky |
| T4.2 | external applications | Nicholas Walton |
| T4.3 | shared storage browser | Pierre Fernique/Dave Morris |
| T4.4 | population of registry | Kevin Benson/Sebastien Derriere |
| T5 | AVO prototype | FrancoiseGenova, CDS |
|---|
| T5.1 | improvements | Francois Bonnarel |
| T5.2 | extensions | Sebastien Derriere |
| T6 | demo event | ChristopheArviset, ESA |
|---|
| T6.1 | local organization | Christophe Arviset |
| T6.2 | technical setup | Fernando Felix |
| T6.3 | definition of agenda | science team |
Task Descriptions
T1 science cases
Responsible: PaoloPadovani, ST-ECF
T1.1 collect SWG feedback and input
Interact with SWG sub-groups to get feedback on previous demos and new scientific needs: summary.
T1.2 definition and selection
Collect ideas for scientific cases and define scenarios together with SWG.
Two scientific scenarios have been selected:
T1.3 data collections and providers
Identify required data sets and their providers.
T1.4 detailed design
Flow charts incl. required input, manipulations, conversion, desired output.
T1.5 execution, produce sci. results
Walkthroughs for both scenarios; execute walkthroughs; capture scientific results.
T1.6 presentation, dissemination
Implementation, discussion, review thereof at demo trial meeting M7.
T2 SED generation
Responsible: MarkusDolensky, ESO
T2.1 data curation
Make data sources accessible; liaise with data providers; implement new access services where applicable; ingest catalogs into Vizier where applicable.
T2.2 special workflow operators
Identify, design and implement operators on SED objects which will either become part of workflows or the AVO prototype's filter functionality.
T2.3 visualization + analysis
Identify requirements of SED user front end; features for analysis and visualization; supervise implementation and testing.
T2.4 SED support library
Work with STScI (Ivo Busko) on a SSA support library for reading and writing spectral data.
AndreSchaaff released SAVOT V2.5 which supports VOTable 1.1, a pre-requisite for manipulating data compliant to an SSA data model.
T3 data center infrastructure
Responsible: KeithNoddle, Astrogrid
T3.1 identify useful middleware components
PAL (SkyNode), MySpace, JES/CEA (workflow); further details below.
T3.2 workflow builder
Tool for building workflows; there will be a GUI which talks to the master registry in Leicester (T3.6).
T3.3 workflow execution and monitoring
Deployment of Job Execution System (JES), deployment of Common Execution Architecture (CEA).
Selecting, triggering and monitoring of workflows is part of the Astrogrid Web Portal and will be re-used in this context.
T3.4 shared storage
MySpace; deployment of file stores and the MySpace controller (server) component.
T3.5 data access layer
Adaptation and deployment of the Publisher's Astrogrid Library (PAL). This includes adapters for ADQL (SkyNodes) and SIA services.
T3.6 master registry
A full registry; AVO partners and data providers will register services and data collections against a registry in Leicester. The registry will harvest at least from Vizier as well as one full NVO registry.
Test system: registry index (Hydra server in Leicester).
T4 integration
Responsible: KeithNoddle, Astrogrid
T4.1 IVOA compliance
Identify minimal standards required for the AVO demo 05; guide data providers and tool builders as which specifications to develop against: http://www.euro-vo.org/internal/Avo/DemoPlan05on20040812/ivostds4avodemo05.pdf
T4.2 application servers
Identify and supervise integration of external applications into workflows. Acquire test data and liaise with application experts and relevant providers as needed.
T4.3 shared storage browser
Integrate a MySpace browser into the AVO prototype load dialog. It'll allow access to workflow input/output data put on distributed file stores.
T4.4 population of registry
Help data and service providers to populate the master registry. Establish functional OAI interfaces to a NVO registry and CDS (Vizier) registry. Provide stable service for demoing.
T5 AVO prototype
Responsible: Main.FrançoiseGenova, CDS
T5.1 improvements
Improvements as described here.
T5.2 extensions
Extensions as described here.
Note: Plug-ins are singled out as separate tasks and some extensions fall under external applications.
T6 demo event
Responsible: ChristopheArviset, ESA
T6.1 local organization
Form LOC; manage logistics of meeting.
T6.2 technical setup
Specify system requirements and H/W needs for demo; provide equipment for M8 and M9:
- for details see Annex 2 of the telecon minutes from Oct 21st.
T6.3 definition of agenda
Form POC, define agenda, planning.
|
|
Edit menu
