This shows you the differences between two versions of the page.
open:wp4:wp4techforum5:radiointhevo [2019/03/13 16:17] bonnarel |
open:wp4:wp4techforum5:radiointhevo [2019/03/13 16:21] (current) bonnarel |
||
---|---|---|---|
Line 17: | Line 17: | ||
I ) **status and feedback on Multi-D and existing standard protocols for radio data** | I ) **status and feedback on Multi-D and existing standard protocols for radio data** | ||
ObstPAP(Obscore)-SIAV2+DataLink+SODA+clients(Aladin) work for imaging cubes (science ready | ObstPAP(Obscore)-SIAV2+DataLink+SODA+clients(Aladin) work for imaging cubes (science ready | ||
- | products) | + | products) |
HiPS works for the same (full 3D HiPS or alternatively 2D continuum HiPS + DataLink access | HiPS works for the same (full 3D HiPS or alternatively 2D continuum HiPS + DataLink access | ||
- | to cubes, Other moment maps SODA). See CASDA (ASKAP) data + partially ALMA. Detailed | + | to cubes, Other moment maps SODA). See CASDA (ASKAP) data + partially ALMA. Detailed |
analysis by INAF. | analysis by INAF. | ||
MOC also useful for discovery. But MOC in velocity could help. | MOC also useful for discovery. But MOC in velocity could help. | ||
Due to the nature of raw data, image sensitivity may change a lot from pixel to pixel .. | Due to the nature of raw data, image sensitivity may change a lot from pixel to pixel .. | ||
- | --> need for sensitivity cubes? | + | --> need for sensitivity cubes? |
Some of the data are complex. ObsCore not really suited for this. Use of CAOM better? | Some of the data are complex. ObsCore not really suited for this. Use of CAOM better? | ||
Coarse grain discovery of raw data (or calibrated discovery) via ObstAP/SIAV2 (or HiPS + | Coarse grain discovery of raw data (or calibrated discovery) via ObstAP/SIAV2 (or HiPS + | ||
- | DataLink) probably possible, but not experimented yet. Links to project native pages for | + | DataLink) probably possible, but not experimented yet. Links to project native pages for |
- | the data can be made available | + | the data can be made available |
It appears that currently most of the data in the radio archives are not science ready. | It appears that currently most of the data in the radio archives are not science ready. | ||
- | So there is a big question mark: why and how integrating visibility/raw data in the VO? | + | So there is a big question mark: why and how integrating visibility/raw data in the VO? |
II ) **Fine grain discovery:** | II ) **Fine grain discovery:** | ||
- | Seems to be needed before retrieving data (due to data volume). Need to define some "data | + | Seems to be needed before retrieving data (due to data volume). Need to define some "data |
- | filters" by characterizing data. | + | filters" by characterizing data. |
- | Visibility characterisation to answer the trustability question: uv coverage = uv ranges, | + | Visibility characterisation to answer the trustability question: uv coverage = uv ranges, |
- | uv power plots, uv distribution maps, amplitude versus spectral frequency, versus phase | + | uv power plots, uv distribution maps, amplitude versus spectral frequency, versus phase |
- | and versus time. | + | and versus time. |
- | Sensitivity or resolution based discovery. For a given target which are the best | + | Sensitivity or resolution based discovery. For a given target which are the best |
- | observations to provide some minimal sensitivity? some minimal resolution ? It seems to | + | observations to provide some minimal sensitivity? some minimal resolution ? It seems to |
- | require information on the beam shape and size. | + | require information on the beam shape and size. |
- | Discovery based on configuration details. : number of antennas, array configuration, etc.. | + | Discovery based on configuration details. : number of antennas, array configuration, etc.. |
- | or others: filling factor, baseline length ... or PROPOSALS. ---> Provenance dM | + | or others: filling factor, baseline length ... or PROPOSALS. ---> Provenance dM |
- | Trustability by examining different calibration steps (provenance also ?) | + | Trustability by examining different calibration steps (provenance also ?) |
- | Apparently some of this stuff can be provided statically, some other stuff can only be | + | Aparently some of this stuff can be provided statically, some other stuff can only be |
- | generated dynamically according to user needs. This is more difficult to provide for large | + | generated dynamically according to user needs. This is more difficult to provide for large |
- | field of views | + | field of views |
Open questions: what does the VO can do for this? | Open questions: what does the VO can do for this? | ||
- integrate additional characterisation feature in existing models (ObsCore) | - integrate additional characterisation feature in existing models (ObsCore) | ||
- | usage of provenance? | + | usage of provenance? |
- Use DataLink to give access to various characterisation or sensitivity | - Use DataLink to give access to various characterisation or sensitivity | ||
features? Including graphically. | features? Including graphically. | ||
- provide dynamical tools: as web services? as Desktop applications? | - provide dynamical tools: as web services? as Desktop applications? | ||
- they can probably be easily integrated in the VO as custom services | - they can probably be easily integrated in the VO as custom services | ||
- | using UWS and DataLink "service descriptor" or applications using | + | using UWS and DataLink "service descriptor" or applications using |
SAMP, registry and DAL communications. | SAMP, registry and DAL communications. | ||
- | - provide more may be cumbersome and outside of the scope of the VO. | + | - provide more may be cumbersome and outside of the scope of the VO. |
- | Last but not least : VO is not in charge of verifying the quality of the data. (No data | + | Last but not least : VO is not in charge of verifying the quality of the data. (No data |
- | police !). VO Validators deal with compliance of services with the standard. | + | police !). VO Validators deal with compliance of services with the standard. |
Line 67: | Line 67: | ||
Among other possibilities: | Among other possibilities: | ||
Web service creating on the fly science ready data (reduction details hidden behind the | Web service creating on the fly science ready data (reduction details hidden behind the | ||
- | service interface) | + | service interface) |
Go back to progenitors of science data using provenance and reprocess. characterisation | Go back to progenitors of science data using provenance and reprocess. characterisation | ||
- | and other metadata information needed to reprocess (see II above) | + | and other metadata information needed to reprocess (see II above) |
Port code to the data and execute CASA or whatever reduction software remotely. | Port code to the data and execute CASA or whatever reduction software remotely. | ||
Store and distribute science data produced by users. Reusability of the data. | Store and distribute science data produced by users. Reusability of the data. | ||
Download data and reduce them with Python VO package tools in Jupyter notebooks. | Download data and reduce them with Python VO package tools in Jupyter notebooks. | ||
- | "Measurement sets" seem to be the most complete and widely used data model for | + | "Measurement sets" seem to be the most complete and widely used data model for |
- | visibility data. Used by VLBI. | + | visibility data. Used by VLBI. |
- | Do we need to tackle other formats (MBFITs, VLBI FITS, PSRFITS for pulsars etc ???) | + | Do we need to tackle other formats (MBFITs, VLBI FITS, PSRFITS for pulsars etc ???) |
- | Do we need to map measurements and metadata to some extensions of VO data models | + | Do we need to map measurements and metadata to some extensions of VO data models |
- | (Cube DM, TS DM, Provenance ?) For which purpose? Exposing what is relevant for | + | (Cube DM, TS DM, Provenance ?) For which purpose? Exposing what is relevant for |
- | other users from the internal model ? | + | other users from the internal model ? |