LUA plug-in: Ephemeris(?) A work in progress...

[Fenerit]

If I try to move the ephemeris box, I have to
completely re-install the whole lua-plugins system in order to get the ephemeris
box back to where it should be. Beats me.

Thanks again, Brain-Dead

Mmm... This seem "to bring water to the mill" for my conjecture above. You simply need to erase the ephemeris_prefs.lua file in the main Celestia root "in order to get the ephemeris box back" like in the first start; if am I in true and just in accomplishing such operation does allow to you the restarting without to re-install all again, it mean that something "lock" the writing of the file in question. Roughly: the file is created when Celestia start and then get locked (whereas the pixels settings within the file must be wrote-in "like the floating values of the HUD's") during the mouse movement. Probably such file is never written from start! hence:
do make a text file in the main Celestia root called ephemeris_prefs.lua and add into it the following strings:

Code: Select all

return {
-- Table: {1}
{
   ["ephemerisBb"] = 484,
   ["ephemerisLb"] = 3,
},
}


then save, and launch Celestia. Try now to move the box, that with such settings you will have on the screen left-hand

[BobHegwood]

then save, and launch Celestia. Try now to move the box, that with such settings you will have on the screen left-hand

After I launched Celestia with the new settings, the box was properly displayed at the upper left-hand display
within Celestia. It was over-written by the "verbose" information I had displayed, so I told Celestia to display
NO information so that I could see the ephemeris display.

Looked fine, but when I tried to move it, the box was immediately relocated to the upper left-hand
portion of the screen. This is the same behavior that it had when I tried to move it from the right-hand
side of the screen.

The good news, though, is that I didn't have to reinstall anything after I copied the original
ephemeris_prefs.lua to a safe location before attempting the substitute. After I copied
the original code back to the Celestia directory, all was fine.

Hope that helps...
Thanks, Brain-Dead

[Fenerit]

.
.
The good news, though, is that I didn't have to reinstall anything after I copied the original
ephemeris_prefs.lua to a safe location before attempting the substitute. After I copied
the original code back to the Celestia directory, all was fine.
.
.

...Therefore Vista read but doesn't write into file, "ipse dixit Philosophus in quatuor libros De Caelo et mundo" Do you have administrators' privilege? Let's go into administration tools > services and remove some protections. Or, at least use such ephemeris_prefs.lua file by writing in it your screen positions (whether you wish your own); this operation is allowed because is made within the OS, but the OS locks programs which attempt to write in "external" way (IMHO).

[BobHegwood]

...Therefore Vista read but doesn't write into file, "ipse dixit Philosophus in quatuor libros De Caelo et mundo" Do you have administrators' privilege?

Yes. I do have administrators privileges, but that's where Vista gets all screwed up.
Even though I am the only user, and even though I have given myself administrator
privileges, often Vista will not accept an administrative command unless I run
the program as an administrator. This is what I do in order to execute Celestia.

Please just do not worry about this stuff on my account. Methinks I would be
better off with a new system and O.S.

Thanks, Brain-Dead

[symaski62]

Fenerit

50000 Quaoar

H = 2.7136; -- mean abs. magnitude of 3899 asteroids from MPCORB data
G = 0.15; -- Slope parameter of 3899 asteroids from MPCORB data

Ast_mag = H + 5 * math.log10 (dsS * dsE) - 2.5 * math.log10((1.0 - G) * t1 + G * t2);

----------------------------------------------------------------

Asteroid

APmag =
Asteroid's approximate apparent visual magnitude by following definition:
APmag = H + 5*log10(delta) + 5*log10(r) - 2.5*log10((1-G)*phi1 + G*phi2).
In principle, accurate to ~ +/- 0.1 magnitude. For solar phase angles > 90 deg,
the error could exceed 1 magnitude. No values are output for phase angles
greater than 120 degrees, since the extrapolation error could be large and
unknown. Units: NONE

========================================================

Comet

T-mag N-mag =
Comet's approximate apparent visual total magnitude ("T-mag") and nuclear
magnitude ("N-mag") by following definitions:
T-mag = M1 + 5*log10(delta) + k1*log10(r)
N-mag = M2 + 5*log10(delta) + k2*log10(r) + phcof*beta
Units: none

[Fenerit]

Bob

Please just do not worry about this stuff on my account. Methinks I would be
better off with a new system and O.S.

Sure; drop off Vista and either return to Xp or jump directly to 7; I don't wish you lack of the Moon's new graphic improvement: the bright limb's movement.

Symaski62

50000 Quaoar

H = 2.7136; -- mean abs. magnitude of 3899 asteroids from MPCORB data
G = 0.15; -- Slope parameter of 3899 asteroids from MPCORB data

1) 2.7136 is the abs. mag. of Quaoar?
2) if not, how do you get 2.7136 as mean abs. mag.? I get 11.491 (44806.61/3899) Yes, my value is a REAL ARITHMETIC mean.
3) for comets I'm stay developing...

[symaski62]

Symaski62

50000 Quaoar

H = 2.7136; -- mean abs. magnitude of 3899 asteroids from MPCORB data
G = 0.15; -- Slope parameter of 3899 asteroids from MPCORB data

1) 2.7136 is the abs. mag. of Quaoar?
2) if not, how do you get 2.7136 as mean abs. mag.? I get 11.491 (44806.61/3899) Yes, my value is a REAL ARITHMETIC mean.
3) for comets I'm stay developing...

1) 19.252 abs.mag

2) 28.030 abs.mag => 50000 Quaoar H = 11.491

3) no

[Fenerit]

Thanks Symaski62 to be interested here. Nonetheless, your comet's formula can get misinterpretations:

T-mag N-mag =
Comet's approximate apparent visual total magnitude ("T-mag") and nuclear
magnitude ("N-mag") by following definitions:
T-mag = M1 + 5 * log10(delta) + k1 * log10(r)
N-mag = M2 + 5 * log10(delta) + k2 * log10(r) + phcof * beta
Units: none

The delta is not the product of asteroid's radius vector * solar distance, but IS just the solar distance ( r is the radius vector Earth/Ast.).

Then:
Ast_mag = H + 5 * math.log10 (dsS * dsE) - 2.5 * math.log10((1.0 - G) * t1 + G * t2); is equivalent to:

APmag = H + 5 * log10(delta) + 5 * log10(r) - 2.5 * log10((1-G) * phi1 + G * phi2)

, in which the delta here is also wrong, being the same as above, that is the solar distance.

For what concern the comets, I'm stay to collect the costants k, then will apply the equation.; so I'm unable to decrypt you "No"

[Fenerit]

Continuing the story...

- Added Sun's position angle;
- Added constellations for planets
- Added theoretical visual magnitudes for all SS objects;
- Minor changes (Earth's sideral period and Moon synodic period are recovered between costants and no longer retrieved by .Info orbital)



In the image above the yellow is the Sun's position angle and its direction while orange are the markers for the bright limb inclination (not the terminator). All the marker turns accordingly with the brigh limb motion.