Planetary hours

[Sindy]

I noticed that PD gives different results for planetary hours than the two other programs I'm using for looking them up (https://planetaryhours.net/, https://play.google.com/store/apps/details?id=com.technologies.mobile.astroclock&hl=en_US&gl=US).

Are the planetary hours in PD calculated differently? Anyone else experiencing this?

[ABer]

Hi Sindy - I'll take a look at it. Can you send me any chart data. It's always useful to look at a specific scenario. Is it generally within PD or within a specific module.

Thanks. Ed

[Sindy]

Hi Ed,

it's in Time/Planetaryhour. Elsewhere in the program, it seems fine.

P. S.: A small thing, but should Planetaryhour be written separate (Planetary Hour)?

[Jean]

The planetary hour code used in horoscope data and on the column was given to me by Ziyad Alawi.
I think Ed also uses planetary hour but i did not compare things.
Examples would be welcome Sindy.

ps i dunno about it's spelling, without space is one character less to type though.

[ABer]

Hi Sindy - first thing - do you have the same location for the different modules. To get the correct planetary hour ruler from the Planetaryhour script, you will have to ensure that you have chosen the correct location to match the location of the chart. Planetaryhour sets the place to the default location unless you manually change it using the Place menu.

Let me know if that fixes your problem.

Ed

[Sindy]

It is not about planetary hours in any chart. It is the general planetary hours in my location I'm speaking about. Below the calculations, Planetdance and the two other programs I'm using give for today.

[ABer]

OK - we'll look into it. Ed

[ABer]

Thanks Sindy - the bug seems to be isolated to the Planetaryhour module. This is calculated using a different algorithm to the other implementations of planetary hours, which, as you say are right.

Jean will have a look at this when he has time.

Ed

[Sindy]

Thanks for the quick response, Ed! There's no hurry with fixing the bug. But good to know that Jean is going to look at it.

[Jean]

I'm not sure i understand what's going on. What the module does is divide the time between sunrise and sunset in 12 equal parts, then it follows the sequence moon, mars, mercury etc to give that planetary hour, the start for that sequence is dependant on the weekday. It also does this for the night.

To calculate rise / set it needs a time, to indicate when to start looking, if i give it the local time it starts the sequence with venus, if i don't correct for timezone it begins the sequence with saturn, just as the websites are reporting. For 'day of the week' to work correctly it needs a local time. So I'm not sure what's going on but i get the same results if i *don't* correct the start of the search for sunset to local time.

So it may work correctly now.

[Sindy]

Not sure if I understand about the correction. Shouldn't the first hour of the day (sunrise) be under the rulership of the planet ruling the day? For Saturday, the first hour is ruled by Saturn. That's how it is displayed in your picture. So, it seems right. But I'm not an expert on the subject. Maybe someone knows better? Where did you do the changes?

[Jean]

Sindy, what do you mean 'Where did you do the changes'?
I just published an update if that's what you mean.

[Sindy]

I did an update but got the same results as earlier, starting the day with Venus.

[Jean]

I'm sorry, I thought i had published it, i did now.

I also found the error in my logic. To get rise/set times UT is needed but to determine weekday local time is needed, i forgot to do that. Now it translates to saturday / saturn correctly.

Another bug fixed Sindy.

[Sindy]

Well done, Jean! 😃 Now, it's working on my PC, too.

Planetdance's direction is perfection! 😁