Incorrect albedo in solarsys.ssc?

Report bugs, bug fixes and workarounds here.
Topic author
Malenfant
Posts: 1412
Joined: 24.08.2005
With us: 19 years 3 months

Incorrect albedo in solarsys.ssc?

Post #1by Malenfant » 29.10.2005, 22:13

The albedos in the solarsys.ssc don't agree with the values found on the NSSDC planetary datasheets and elsewhere (eg my RASC Observer's Handbook).

Currently they are (in both pre7, the cvs source, and FT1.1):

Code: Select all

Mercury         0.06
Venus         0.77
Earth          0.3
Moon          0.12
Mars          0.15
Jupiter          0.51
Saturn          0.50
Uranus          0.66
Neptune          0.62
Pluto          0.55


IN the NSSDC datasheets (and other 'official' solar system data sources) they are:

Code: Select all

Mercury         0.106
Venus         0.65
Earth          0.367
Moon          0.12
Mars          0.15
Jupiter          0.52
Saturn          0.47
Uranus          0.51
Neptune          0.41
Pluto          0.5 - 0.7


These are visual geometric albedos (the ssc values are also very different from the Bond albedos, but I presume you're using geometric (visual) albedos here). Note though that the values for the Moon and Mars are the same in both the ssc and the NSSDC data.

I haven't checked every single body in the ssc file yet, but certainly it seems to me that these ones should be corrected!

Topic author
Malenfant
Posts: 1412
Joined: 24.08.2005
With us: 19 years 3 months

Post #2by Malenfant » 31.10.2005, 16:24

Is this a known bug or something? I thought someone would have commented on this by now.

Or was it just a slow weekend? ;)

Avatar
selden
Developer
Posts: 10192
Joined: 04.09.2002
With us: 22 years 2 months
Location: NY, USA

Post #3by selden » 31.10.2005, 16:53

Those values have been there since the beginnings of Celestia: those are the values that are in v1.0.10, the earliest version on SourceForge.

I suspect you'll have to persuade Chris to update them.
I'd suggest posting corrected values to the developers' mailing list.
Be sure to cite a specific source for each of the values you send.
Selden

Topic author
Malenfant
Posts: 1412
Joined: 24.08.2005
With us: 19 years 3 months

Post #4by Malenfant » 31.10.2005, 17:12

selden wrote:Those values have been there since the beginnings of Celestia: those are the values that are in v1.0.10, the earliest version on SourceForge.

I suspect you'll have to persuade Chris to update them.
I'd suggest posting corrected values to the developers' mailing list.
Be sure to cite a specific source for each of the values you send.


OK, Selden. How do I get onto the mailing list?

I'm surprised nobody noticed this difference before (particularly Grant. I thought he updated these ssc files a lot?).

Avatar
selden
Developer
Posts: 10192
Joined: 04.09.2002
With us: 22 years 2 months
Location: NY, USA

Post #5by selden » 31.10.2005, 17:47

http://lists.sourceforge.net/lists/list ... developers

Grant was primarily interested in getting the orientations correct.
The albedo values only affect the brightness of the dot that's drawn when an object is too small to resolve.
Selden

Topic author
Malenfant
Posts: 1412
Joined: 24.08.2005
With us: 19 years 3 months

Post #6by Malenfant » 31.10.2005, 18:07

selden wrote:http://lists.sourceforge.net/lists/listinfo/celestia-developers

Grant was primarily interested in getting the orientations correct.
The albedo values only affect the brightness of the dot that's drawn when an object is too small to resolve.


Well I only noticed it myself because I need the albedo for my planetary magnitudes script.

BTW, can we add our own terms to an ssc? Say for example I wanted a Bond Albedo as well as a geometric one, could I add that to the ssc (as BondAlbedo or something) even though Celestia itself wouldn't use it? Or would the ssc not render because there's stuff in there that Celestia doesn't understand? (just asking out of curiosity, not got anything planned here... )

Avatar
selden
Developer
Posts: 10192
Joined: 04.09.2002
With us: 22 years 2 months
Location: NY, USA

Post #7by selden » 31.10.2005, 18:15

Unfortunately, Celestia will generate an error and stop reading the SSC file if you include a keyword that it doesn't know about. For example, I often insert "exit" in SSC files when I want the stuff after that point to be ignored.
Selden

Topic author
Malenfant
Posts: 1412
Joined: 24.08.2005
With us: 19 years 3 months

Post #8by Malenfant » 31.10.2005, 18:26

OK, so I guess I'd just have to include any extra numbers I wanted in the script itself.

BTW, Celestia does support "Mass" as an entry in the ssc, yes? Can you declare masses for stars and planets, or just stars? And what are the units?

Avatar
selden
Developer
Posts: 10192
Joined: 04.09.2002
With us: 22 years 2 months
Location: NY, USA

Post #9by selden » 31.10.2005, 18:45

You might want to consider including your desired parameters in the catalog file, but have them commented out.

Although Celestia does accept the SSC keyword "Mass", and sets a value named "mass," it otherwise ignores it completely. There is no code using it, so there are no implied units.
Selden

Topic author
Malenfant
Posts: 1412
Joined: 24.08.2005
With us: 19 years 3 months

Post #10by Malenfant » 05.11.2005, 17:39

Well I posted on the developers list a few days ago and have had no response or comment at all. Looks like everyone's gone back to sleep there.

I know Grant pops in occasionally here... Grant? Do these need updating? It seems to me that they do.


Return to “Bugs”