ESASky User Forum / Whiteboard

Welcome to the ESASky user forum! The aim of this forum is to have a place to collect feature requests from users, allow conversations between users and gauge the Astronomy community's priorities related to the ESASky application. We welcome requests for the ESASky, its documentation, its ways of interacting with the community, and any functionality which you think would be widely useful to the Astronomy community.

Please suggest and vote on feature requests below. Before adding a new suggestion, use the search function to see if the idea has already been posted. Please include links to relevant repositories and existing issues in the description of the feature request. Also consider including links to code or images demonstrating the requested functionality.

You can also use this forum to report bugs or request small improvements to existing functionality.

Other places to get help and communicate with the ESASky team are:

The ESASky Project is dedicated to maintaining a positive, inclusive, successful, and growing community. Please observe the usual basic internet citizen rules before posting to this forum.

0
Fixed

Inaccuracy in the description of the positional error in the Chandra catalogue.

Ricardo Pérez Martínez 7 years ago updated by anonymous 7 years ago 3

In the description of the Chandra catalogue, the column related to the positional error is defined as 

Position error radius at 95% confidence level   //  arcsec   // Position error 95% confidence level circle radius (column also called err_ellipse_r0)

While in the Chandra web page, err_ellipse_r0  is said to be something different

Three of the parameters specifying the geometry of each error ellipse are the semi-major and semi-minor radii (/err_ellipse_r0/, /err_ellipse_r1/), and the position angle θ that the major axis of the ellipse makes with respect to the tangent plane /y/ axis (/err_ellipse_ang/).

What is not actually the same. The difference can be specially relevant when cross matching several set of catalogues/source lists at once.

Answer
anonymous 7 years ago

Dear Ricardo,

We are happy to report that the problem you reported has been fixed in version 2.0 of the ESASky application: http://sky.esa.int

Enjoy!

Bruno

on behalf of the ESASky team

0
Fixed

In the "soft Xrays layer" CDS EPIC PN, hips are not displayed

Nora Loiseau 7 years ago updated by Deborah Baines 4 years ago 4
0
Started

Auto-import of gamma-ray bursts or other transient events

Peter Kretschmar 7 years ago updated 2 years ago 3

The Gamma-ray Coordinates Network (GCN) or Transient Astronomy Network (TAN) distributes information about gamma-ray bursts or other transient events in (near-real) time via different services, including VOEvents.

https://gcn.gsfc.nasa.gov/

It could be interesting for multi-wavelength follow-up campaigns to have an interface allowing view of burst/transient positions in ESASky, including the reported position uncertainties and which is built automatically from the GCN/TAN alerts. The view should evidently allow filtering on categories like time, event category, source ...


This is an idea for the longer term.