Open cdeil opened 7 years ago
I've added a link to the docs as part of #70 . Keeping this issue open as a reminder to discuss, but moving it to the 0.2 milestone.
I think it's clear that both ipyaladin
and hipspy
will remain by now. So the action item here is to explain the relationship a bit better at https://hips.readthedocs.io/en/latest/about.html, similarly as in the paper or even using exactly text from there.
It should be short, but there should be some infos when to use this hips
package, and for which tasks which other HiPS tool to use (e.g. ipyaladin or Aladin or hipsgen). A 1 or 2 min read intro / guidance for users.
@adl1995 - Maybe this is a docs improvement you could make?
@tboch - I saw your tweet announcing https://github.com/cds-astro/ipyaladin
I haven't figured out yet how to activate it, because I always
pip install --user
, but that's a problem I have for all iPython widgets, not an issue with your package.I think for now, maybe we should at least mention it at https://hips.readthedocs.io because people that find this project will also be interested in
ipyaladin
? Can you make a small docs PR or should I?It's not clear to me how
ipyaladin
and thiships
package relate, long-term. I mean both can fetch and draw and return a numpy array. Do you have any thoughts on this already or should we simply discuss in a few weeks when you're back from vacation?