You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
This page lists requests sent / to be sent to IVOA discussion groups to accommodate VESPA needs.
Interop May 2017 (Shanghai)
All this to be discussed in advance on mailing lists.
Action | from | to | purpose | status |
---|
Ask to include VESPA related tools in IVOA Application lists: - VESPA : http://vespa.obspm.fr web application, EPN-TAP (and PDAP) client / Query databases connected to VO tools via SAMP
- APERICubes: http://voparis-apericubes.obspm.fr web-based tool Spectral cube slicer for PDS3 formatted cubes (VIRTIS on Venus-Express and Rosetta currently) connected via SAMP (both I/O)
- 3Dview, CASSIS and AMDA have been upgraded to include an EPN-TAP specific client (3D view is not yet included in page http://www.ivoa.net/astronomers/applications.html)
| SE | helpdesk & Mark Taylor | Advertise VESPA developments | |
UCDs and Utypes for Solar System - See list in EPN-TAP V2.0 parameters (related to parameters) UCDs in red and italics/blue are non standard but needed by VESPA. - Measured levels: UCD do not exist for our basic measurements… (except flux, which only stands for non-resolved sources) - Usual quantity is radiance, looks like phys.luminosity;phys.angArea in SDM - weird! - see also phys.flux.sb ??? - Define instead phys.radiance ?
- The other std quantity is reflectance = I/F - I/F would be arith.ratio;phot.flux.density - not even sure because this is the ratio of a radiance to a flux (in sr^-1) - We also need other quantities for lab data (radiance coefficient, various albedos, etc) - Most are dimentionless, but use different scales => extend spectrum data model (or UCDs) ? - phys.albedo in UCD 1.23, not very specific - phys.reflectance for I/F? - And for normalized quantities?
| SE | ? | | |
Spectroscopy How do we pass Utypes and UCDs to VO tools? Really included in VOTables only, not in fits ? The reason is apparently related to the length of value fields in fits. Add fits kw for UCD (and Utypes, if space permits)? Otherwise, data handling in tools depends on how data are transmitted. | SE | | | |
ADQL additions - we need to look inside a field of list, ie to combine ivo_hashlist_has with LIKE e.g. to look for a UCD in a list (and get time vs time;stat.min) | SE | ? | Support of UCDs in measurement_type in particular, but also instrument names, etc | |
Tools / standards: • Spectral aggregates? Required to plot measurements from spectrometers with several channels (very common in our field) • Aladin (to be discussed directly with PFernique?): See fits format items + stability issue of v9 on Mac / java 1.8 (blocks on my machine at startup very often) + issue with auto hips from files, does not work as expected, and never finishes on my side + implement E-handed frames in s_region (see STC item) | SE | ? Pierre Fernique | | |
Fits format: - Chiara's request for additional keywords
- Need to implement the planetary ref systems in Aladin, they are part of the fits std:
MALN + MALT, etc + proj types (see her ex Mars & Venus) - Define equivalent for Earth (don't seem to exist)
- Current fits keywords do not allow for image projections on ellipsoids, even less on a 67P
(one kw missing, see Chiara's docs)
| SE / Chiara Marmo | ? | | |
STC, etc: - s_region is very nice, but we need a E-handed system with longitudes [0, 360[.
Should we add another predefined system (BODY, or BODY-FIXED, or E-HANDED? ) We're currently using UnknownFrame, appears to be W-handed also (used like this in Aladin at least). Or combine UnknownFrame with something else?
| SE | Arnold Rots? | Support of body fixed frames, consistency with IAU conventions | |
| | | | |