Versions Compared

Old Version 5

changes.mady.by.user Anna Kapinska

Saved on

compared with

New Version Current

changes.mady.by.user Stephan Witz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

curl -d 'SUBMIT=Submit+Query&QUERY_MODE=Prepare+Download&PROJECT_CODE=AS1037' https://archive.nrao.edu/archive/ArchiveQuery (the download directory would also be a parameter=value)


Additional requirement:, scriptable queries should in no way impact the production archive system: it shouldn't be possible for giant, frequent or parallel searches to knock the pipelines, ingestion and so on, offline.


Example Use Cases:

  1. A user that has identified a transient event from other means (e.g., ZTF or Rubin), wants to see if calibrated data are available in the archive from VLASS. So the user would want to query on position with some search radius, only for VLASS data in the project title or FSID, and perhaps limited in time. In addition to the return of EBs and images, the user may also want to download the list of returned images and they should be able to do so without going to the web search interface. The user may also want to open those images in CARTA rather than downloading, which should also be a supported option. There should be an ability to request a CARTA session and the user is provided their URL for viewing.
  2. A user plans to propose for VLA time toward a particular object. They search what's available and want to see how good those data are. So the search return should provide EBs, images, and the image metadata which should include the RMS sensitivity, and beam size information. A user should also be able to directly download that image through the search interface or open the image in CARTA, in which case we would need a way to direct the user to the CARTA session by opening their browser or by returning a link within the archive interface.
  3. A user wants to see what data are available toward a science target. There are three EBs available with calibrations in the archive. The user wants to request those EBs as calibrated measurement sets.

  4. (from A. Ginsburg) A user has a program being executed in separate SBs and wants to download the data as soon as they are available.  They'll regularly run queries (cronjobs) to determine if new data are available and trigger the downloads.  (this is a common case for large programs, e.g., the X-program)

  5. (from A. Ginsburg) A user wants to monitor the variability of a quasar that is commonly used as a calibrator.  They should be able to search for all programs that included that target as a calibrator or science target and the integration time and coverage from each observation.

  6. (from C. Casadio/User Helpdesk Ticket) A user wants to search database and download all VLBA data for 5000 sources, with the ability to select the observation(s) with the longest time on source. They should be able to do it all in a one query without human intervention for download (e.g. pop up window).



References:

VO Concepts: https://ivoa.net/deployers/intro_to_vo_concepts.html

...