Skip to content

Aladin Lite issues and feature requests

Christoph Deil edited this page Aug 4, 2017 · 11 revisions

This is a list of issues and feature requests we're having with Aladin Lite for the implementation of http://gamma-sky.net A collection of questions (things we weren't able to figure out by ourselves) and notes of things we'd like to discuss with Thomas

Issues

  • Can we set the order of the catalog markers in the Aladin Lite configuration panel? (i.e. TeV at the top, then 3FHL, 3FGL, SNRcat.)
  • Is it possible to display a local HiPS that has only order 0, 1 or 2 (it works for 3, but not lower order?)
  • There's some drawing bugs with the Fermi color image at low resolution (lines between tiles, and some tiles at the edges missing in the default SIN projection). These drawing issues aren't present in Aladin Desktop, it seems to have a better algorithm?

Bug reports

#1: Incorrect symbol in Aladin-Lite FOV label

But I don't see this bug on Aladin Lite's website. Has this been fixed in a more recent version of Aladin Lite?

#2: Cannot read property '0' of null

This error message appears on gamma-sky.net and Aladin Lite's website. I've noticed it when you pan any image, while the FOV is zoomed out to ~180° (i.e. I didn't notice this issue when zoomed in on a survey.)

#3: Cannot read property 'style' of null

This error message appears on gamma-sky.net and Aladin Lite's website. It happens when you pan the map using a double-click with the mouse.

Feature requests

  • Can we control the order of the list of images the user can select?
  • Instead of being limited to the default surveys in the list of images, can we select any survey available on the CDS HiPS list, perhaps using a search bar?
  • Can we set a custom local HiPS map as the default image?
  • Is it better to use an allsky JPEG or a low HiPS order?
Clone this wiki locally