Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

body disc indication #1130

Open
axd1967 opened this issue Jun 15, 2020 · 7 comments
Open

body disc indication #1130

axd1967 opened this issue Jun 15, 2020 · 7 comments
Labels
enhancement Improve existing functionality importance: low Small problem, rarely visible, no crash

Comments

@axd1967
Copy link
Contributor

axd1967 commented Jun 15, 2020

Is your feature request related to a problem? Please describe.
In cases of very low illuminated sides, bodies (planets, moons) are barely visible. In case of a transit/occultation of a body by another body, it is very difficult to see when the occulted body becomes visible again.

Describe the solution you'd like
A toggle option to draw a circle that indicates the apparent disc This toggle should be independent of the "show/hide planets" option so that the user can choose whether to show bodies and/or discs.

Optionally, the disc would get a dotted/dashed appearance where (partially) hidden (so as to avoid color/night vision issues).

Describe alternatives you've considered
There is no alternative.

Additional context

Venus hding behind the Moon (2020-06-19) - works barely because of the small sickles.

image

but here, it is almost impossible to see Venus appearing behind the Moon

image

Imagine this is then transmitted to YouTube: it becomes very difficult to follow this phenomenon.
Once there is an option to draw circles for bodies, this is ok.

And if possible, this would be nice to have:
image

@gzotti
Copy link
Member

gzotti commented Jun 15, 2020

We had complaints that showing the invisible edge of the planet/lunar disk, esp. in daylight, is "false", "misleading", "unrealistic". You cannot serve all...
This could probably solved with some shader "edge" effect. Wizards, go ahead!

Grids: #485, but we need #502 before that to get the numbers right.

In any case, don't trust the times for Venus occultation, expect a minute of deviation or so. If you observe, please report GPS time with seconds, and your exact location, for "Venus hidden" and "Venus fully visible again". We can use such critical records for testing when aberration may be solved one day.

@gzotti gzotti added enhancement Improve existing functionality importance: low Small problem, rarely visible, no crash labels Jun 15, 2020
@axd1967
Copy link
Contributor Author

axd1967 commented Jun 15, 2020

yes, I don't expect sub-minute accuracy, I'm happy to live with this limitation, I understand this is part of Stellarium limits.

very good, thank you for suggesting to collect timings that can be used to check the model!

but sorry, those who complain about misleading should simply not use the toggle, let those that appreciate the feature use it. there is a clear use case where we need this, and technically it is very easy to do. or maybe make this an option that can only be set via config and keyboard, not via GUI?

@axd1967
Copy link
Contributor Author

axd1967 commented Jul 4, 2020

So, this is acceptable (and more realistic), but the disc that would replace the exact same dimensions would not be realistic? But both show exactly the same information?
image

@axd1967
Copy link
Contributor Author

axd1967 commented Oct 2, 2020

some freewheeling...

the astrocalc dialog uses this information:

const double s1 = object1->getSpheroidAngularSize(core);
const double s2 = object2->getSpheroidAngularSize(core);
const double d1 = object1->getJ2000EquatorialPos(core).length();
const double d2 = object2->getJ2000EquatorialPos(core).length();
if (mode==PhenomenaTypeIndex::Opposition) // opposition
{
phenomenType = q_("Opposition");
// Added a special case - lunar eclipse
if (qAbs(separation) <= 0.02 && ((object1 == moon && object2 == sun) || (object1 == sun && object2 == moon)))
phenomenType = q_("Eclipse");

this could be used to compute the radius of the eclipsing body disc. admitted, (1) precision is not excellent (but again, the same problem happens when the user uses a fully illuminated eclipsing body instead - this is also wrong, but this cannot be prevented) and (2) a spheroid should not be drawn as a circle, and (3) eclipsed bodies might also need to be drawn correctly (correct angular size, with a minimum of x pixels, in order to stay visible).
but it is a first approximation in order to go forward in this issue: to give some indication where the eclipse ends in case this happens on the dark side. but this does not solve the issue completely: the eclipsing body must be replaced by the body circle because the idea is to see where the eclipsed object is behind the eclipsing object.

an option "discs only" (tooltip: "this replaces all solar system bodies with circles in order to better see eclipse start/endings") could be added in the View/SSO tab + keyboard shortcut to easily toggle the option.

eclipsing bodies can be Sun, Moon, planet.

(the hint circle is unusable, in fact a texture:)

Planet::hintCircleTex = StelApp::getInstance().getTextureManager().createTexture(StelFileMgr::getInstallationDir()+"/textures/planet-indicator.png");

image

@axd1967
Copy link
Contributor Author

axd1967 commented Oct 2, 2020

another example where a body disc is handy

image

by lack of a disc, a telrad ring is used (but one cannot see what is happening behind the Moon disc).

(the text hint is missing, the Moon is just too close for it to appear)

@axd1967
Copy link
Contributor Author

axd1967 commented Feb 23, 2021

compare with #430: a disc that would draw the outline of the current Moon (simulated here by the Moon simulating the eclipsed object , and the umbra simulating the Moon...)

image

image

@axd1967
Copy link
Contributor Author

axd1967 commented Oct 13, 2021

See also "disco ball" in this #1924 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improve existing functionality importance: low Small problem, rarely visible, no crash
Development

No branches or pull requests

2 participants