Make it possible to choose between multiple planetary HiPS per planet#4459
Make it possible to choose between multiple planetary HiPS per planet#4459
Conversation
Not only is this very inefficient, but it also resets the expandedness state of tree items, which needs careful management. Now we simply don't touch the items already present.
|
Great PR! Please pay attention to the following items before merging: Files matching
This is an automatically generated QA checklist based on modified files. |
|
Nice addition! I like the various moon maps. Any clue why they are reversed? (Or why ours are reversed if the other ones fulfill some standard?) Also, frequently a message pops up "This group of surveys doesn't have an albedo map. Can't display it". I then have these trouble to disable displaying the survey. |
I don't reproduce this. Could you make a screencast or something to show this?
I guess theirs should be right, after all they are more actively interacting with the authors of the HiPS standard. As to why ours is different, I suppose it's because Guillaume didn't know better when he was implementing it, and now it's a matter of backwards compatibility. Now I also wonder if I should follow the reversal in my Moon survey too, before it's too late.
OK, the failure to disable the survey after the message is a bug, I'll fix it soon. As for the frequent popup, it's because you're supposed to disable the group if you don't want any survey to be shown, or just enable another survey from the group if you want to switch to it (the previously selected one will be unchecked automatically). Maybe there's a way to make UX better, any ideas? |
|
How does one add your Moon survey? It doesn't appear in the list. |
SUG chapter 10.2.
It should appear by the group name: |
|
Hello @10110111! Thank you for the suggested improvement. |
The planetary surveys from alasky.cds.unistra.fr appear to have a reference frame that's rotated by 180° in longitude relative to that of Stellarium's planetary surveys. These surveys were created by Aladin/HipsGen, which I assume to be more or less a reference implementation. Since we can't easily change Stellarium's frame without backwards compatibility issues, and the "type" field is a custom field not used outside of Stellarium, we can use it as an indicator whether we need to fixup the coordinates of a survey.
|
After a few more commits it's even more important to keep them separate when merging. But at least now I've addressed all the comments here as well as a few issues I've found. Are there any objections to merging this? |
Just stumbled upon this code in // Apply a rotation otherwise the hips surveys don't get rendered at the
// proper position. Not sure why...
painter->getProjector()->getModelViewTransform()->combine(Mat4d::zrotation(M_PI * 0.5));
...
// Undo the rotation we applied for the survey fix.
v = Mat4d::zrotation(M_PI * 0.5) * v;And this comes from the very beginning, #110, namely this commit. I'm still not sure what exactly would go wrong if this kludge weren't included. Maybe Guillaume thought that his HiPS were correctly generated while they weren't, and introduced this workaround into the C++ code, breaking the actual HipsGen-generated surveys. In any case, this is working now, but the code contains two rotations: one in |
|
Hello @10110111! Please check the fresh version (development snapshot) of Stellarium: |
|
Hello @10110111! Please check the latest stable version of Stellarium: |
Description
Currently we can only have one HiPS pack per planet (albedo, normals, horizons). This PR enables multiple HiPS per planet to choose from.
The surveys are arranged into groups, with the groups defined either by
groupproperty of a set of surveys, or by the hipslist's URL.To test this, you can use my new Moon survey pack: http://86.106.181.97/hips/hipslist. Additional set of surveys can be obtained from this URL (with a nuance that their coordinate system is shifted by 180° of longitude with respect to ours, which should be taken care of in a later change). And there's also the default Stellarium surveys that are normally removed if you set custom ones in the config file: one, two.
If you are going to merge this, please keep the commits separate.
Type of change
How Has This Been Tested?
Test Configuration:
Checklist: