Tus comentarios

Besides the issue above, we identified a nice protoplanetary disk in the asteroidhunter.org zooniverse project here:


https://www.zooniverse.org/projects/sandorkruk/hubble-asteroid-hunter/talk/2451/1381172


and when I try to search for this interesting object in ESASky, I cannot see the image in the WFC3 HiPS, even if the observation was done in January 2015..

Thanks Jonas!

For reference to others, the pyESASky 1.0 software is available for download at

https://github.com/esdc-esac-esa-int/pyesasky

The whole idea behind this project is precisely to allow people mixing their local data or data in any online service with what is is in ESASky already. Let us know whether this might be not be working fine for you for any reason.


We know about the JupyterLab problem and Fabrizio is looking into this now..

The documentation has been fixed to explain how to set the coordinate format for target lists.

The requested bug fix has been implemented in version 2.1.

Please let us know if you experience it again.

Thanks Nora, indeed that is was in the list but did not have a ticket, so now I created one. We will let you know once this has been implemented.

Good suggestion. In general, when the target lists are given with coordinates, ESASky uses the galactic or ra/dec frame that is currently selected, regardless whether the coordinates are given with two floats or in hexadecimal format (which is more typical of ra/dec coordinates). We have updated the documentation of this feature on the online help:


https://www.cosmos.esa.int/web/esdc/esasky-target-lists


Is that good enough?