1 / 13

Solar Orbiter Archive (SOAR)

Access the scientific archives of Solar Orbiter & other space missions for astronomy, planetary science, & heliophysics. Follows ESA PI mission data archiving model with controlled access for instrument teams and observers.

adamski
Download Presentation

Solar Orbiter Archive (SOAR)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Solar Orbiter Archive (SOAR) Pedro Osuna Solar Orbiter Archive Scientist

  2. ESAC At ESA’s European Space Astronomy Centre near Madrid Science Archives from >15 space missions: Astronomy, Planetary, Heliophysics From all phases (development, operations, post-ops, legacy) http://archives.esac.esa.int/ Different Users: Scientific Community (public access) Instrument teams and observers (controlled access) Science Operations Team (privileged access)

  3. SOLAR ORBITER ARCHIVE (SOAR) from Science Management Plan • […]Data archiving for Solar Orbiter will follow the same model as previous ESA PI missions in the solar and heliophysics domain (e.g., SOHO). […] Reduction of science data is under the responsibility of PI teams. • Following in-orbit commissioning, the PI teams retain exclusive data rights for the purpose of calibration and verification for a period of 3 months after the receipt of the original science telemetry and auxiliary orbit, attitude and spacecraft status information. • Upon delivery of data to the ESA SOC, it will be made available to the scientific community at large through the ESA science data archive […]

  4. Current status • SOAR BETA(v 0.5.0) : http://soardev.esac.esa.int/soar-beta/ • https://issues.cosmos.esa.int/socciwiki/display/SOAR/ESDC-SOAR-RN-0.5.0+Release+Notes • Somefunctionalitieswill be availablelike in thecurrent Proba-2 archive: • P2SA BETA (v 0.3):   http://p2sa.esac.esa.int/p2sa-beta/

  5. Snapshots

  6. Machine Interface access • Implements the TAP protocol (http://www.ivoa.net/documents/TAP/) • Allows machines to access the archive contents programmatically bypassing the User Interface • Will also give service to any external applications that want to access any type of data within the archive (see later) • Currently available Synchronous public access. Further implementation will include Asynchronous and Proprietary data access (see next slides) • Can check the available documentation and help at: • http://soardev.esac.esa.int/soar-beta/#aio

  7. TAP Examples - metadata • Metadata requests (access “Machine Interface” left menu, then “Metadata Request” at the right menu)

  8. TAP Examples - data • Datarequests (access “Machine Interface” left menu, then “Data Request” at the right menu)

  9. Proprietary data access and protection • ESAC archives allow for a plethora of different access protection mechanisms, e.g:

  10. Proprietary data access • For SOAR we plan to implement a system similar to the “Table administration” mechanism available for Gaia. This will allow nearly any type of definition of data proprietary rights that we could think of • This would allow to protect data for interchange “on a good-will basis” among the PI Teams • SOAR archive will contain all products delivered to it, from Telemetry to Planning files, LL01, LL02, L1, L2, L3 – we can use it (right now!) for data interchange among institutions – whenever proprietary data are available we will implement the data access policy in a seamless way • Therefore we offer the SOAR as an access point to the data that external institutions (AND applications) can use during whatever mission phase and with any data access restrictions needed as data sharing policy

  11. Pedro.Osuna@esa.int Thank you!

More Related