GithubHelp home page GithubHelp logo

radiovoimplementation's People

Contributors

baptistececconi avatar bonnarel avatar harrisonbarlow avatar jd-au avatar kettenis avatar molinaro-m avatar pahjbo avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

radiovoimplementation's Issues

Proposed update to section 2.5

The current sentence:

Dataproduct_type “timeseries" may be ambiguous for dynamic spectra, so a dataproduct_subtype can be used, or a new dataproduct_type may be introduced.

could be replaced by:

Dataproduct_type “timeseries" may be ambiguous for dynamic spectra, so a dataproduct_subtype can be used, or a new dataproduct_type may be introduced, following the EPNcore dataproduct_type list, which includes a dynamic-spectrum type.

tittle suggestion : "Implementation review "

I suggest to change the title to "Radio astronomy in the VO: services implementation review" .

it reflects the review on all services considered in this IVOA Note.

usually , the Implementation Note document is more a way to explain what to do for implementing a new IVOA specification .

what do you think?

Typo: MWRA -> MWA

In section 3.1, the line:
ObsTAP services: ATOA, MWRA (section A.10), ASKAP, JIVE (section A.8)

should read:
ObsTAP services: ATOA, MWA (section A.10), ASKAP, JIVE (section A.8)

Comment on Section 3 (Raw Data)

To me, the important point here is to foster interoperability and convergence: either by promoting or recommending a sub-set of formats (which is not what we want to do, as written in the note), or providing metadata mapping between the metadata of those products and the IVOA data models.

In this sense, mentioning "HDF5" as a valid format is not enough, since, it doesn't tell anything on the metadata dictionary in use. LOFAR has setup a list of ICD documents specifying how various dataproduct types shall be serialized into HDF5. That should be taken as a good practice, and might be a starting point. Listing other HDF5 flavours would also be good.

Authors of the note

The current author list refers to the RadioIG members. Shall we add names explicitly?
I think it would be more fair to authors who participated in the document edition, in the preparation of the note through the discussion workshops.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.