Calculator worked perfectly for me, even with the reset. The 18:07 CT portal appeared, albeit a couple minutes later than predicted.

Nothing has changed at the update of the server!
The calculator produce correct times since the beginning and I have verified it now:
I had a portalevent at cavern time 03/06/07 18:10 MST (=03/07/07 02:09:40 CET).

@ShadowMan:

Yes, there are some timewindows. I had a chat with some friend 2 days ago and his portal was 6 minutes later than mine!

juri1at wrote:

I had a chat with some friend 2 days ago and his portal was 6 minutes later than mine!

Same. I was talking to someone in Negi at the same time, and I'm still not sure if there portal's shown up yet. XD

Darned 0 seconds and black screen bugs ... still haven't gotten it yet

Never mind, it'll happen in due course

Can you please post a list of the next couple times for those of us on the west coast? Sorry, I'm not good with time zones

Miky714 wrote:

Can you please post a list of the next couple times for those of us on the west coast? Sorry, I'm not good with time zones

First try my tool at the beginning of this thread: http://www.mystonline.com/forums/viewtopic.php?p=124753#124753. There open the spoiler and click onto the image.
If your PC is well configured then you have only get the next events in the first column (Midday / portal events).
If your PC does not set the correct timezone, then change manualy the 'local timezone' to 'Pacific Standard Time (PST) UTC-8'.

This portal calculator is reaching a level of complexity that is a little extreme.

The day length defaults to add seconds and milliseconds, something we have no where NEAR enough data to start confirming

The start time asks you to put in a "midnight" time to predict a portal appearance. That midnight time is calculated by the portal event itself. Not good to use circular logic to ask the program to find a portal time based on a midnight time that was calculated by from another portal time.

There are so many options on the screen that people are not easily able to use the program. Evidenced by people asking to post a list of times so they don't have to fiddle with the program. Its a nice program - don't mistake my intention. But it is not easy to use, and has far too many options that can cause people to end up with wrong times. Not something we want.

Some suggestions:
- Change the default time back to 15h 43m. Leave the seconds off because we cant begin to figure that out yet.
- Remove the "midnight" start time option because that value is not easily calculated unless you already know the portal time to start with. No real reason to use the calculator if you know that much.
- Remove the "local timezone" box because it seems the drop down boxes beside the "portal start time" serves the same function, or at least Can. You already have the "show time" options to display times in any timezone.

Just to simplify it for the average user.

Overdrive, you know the complete day length now. Marten extended your research. It's 13 D'ni hours. You'll need Marten's post or the clock pamphlet. I don't have a clock in my bevin, so I don't have the pamphlet.

I'm actually of the opinion that the day length is shorter than 15h 43 mins. Which is why i've been testing times using 42 minutes. I think my offset was set too early though, but I need more time. Pardon the pun. The times were shifting slightly to the end of the portal "windows" leading me to think its somewhere between 42 and 43 mins however detail like that needs many many more samples.

But I've been out of the loop, my brain hurt, and my sleep schedule was ruined for a while. I can't seem to find the topic if you wouldn't mind linking it

Edit: nvm found it.... not a topic

Last edited by Overdrive on Wed Mar 07, 2007 1:23 pm; edited 1 time in total

Yes, Overdrive, the same to me, the calculator getting more complex and more complex.
Therfore I implement an standard and an export-mode.

The 15:43:04.83 came from this posting:
http://www.mystonline.com/forums/viewtopic.php?p=125202#125202.

Thanks, juri1at. That was the post I had in mind earlier.

Overdrive, if you want to time the day length exactly, you'd have to be the only one there. From what I saw when getting my wedge, the server can't handle everybody getting the portal at the same time, so they're deployed over a period of maybe a few minutes.

Rusty_Russell wrote:

Thanks, juri1at. That was the post I had in mind earlier.

Overdrive, if you want to time the day length exactly, you'd have to be the only one there. From what I saw when getting my wedge, the server can't handle everybody getting the portal at the same time, so they're deployed over a period of maybe a few minutes.

I know about the described window that lets the portal cascade, which is why I'm trying to find the very first report of a sighting. I've personally witnessed being one of the first to see a portal, and wait for others to get through, and also been one of the last to get through after hearing reports of others getting in minutes before me.

Its a matter of ultimately finding the average time and warning people to be there a few minutes early. Determining the appropriate offset and the average time will allow for extreme long term forecasting with minimal compounding error which is what I think this program is designed to do.

juri1at wrote:

The 15:43:04.83 came from this posting:
http://www.mystonline.com/forums/viewtopic.php?p=125202#125202.

If 13 Pahrtahvotee is really right than the time span is: 13 * 25 * 25 * 5 * 1.39285737931

EDIT: Fixed typo 25 -> 5

_________________

[KI again #01792364]| Uru images | KI guide

Last edited by Tiran on Wed Mar 07, 2007 3:15 pm; edited 1 time in total

Tiran wrote:

juri1at wrote:

The 15:43:04.83 came from this posting:
http://www.mystonline.com/forums/viewtopic.php?p=125202#125202.

If 13 Pahrtahvotee is really right than the time span is: 13 * 25 * 25 * 25 * 1.39285737931

Does that convert down into seconds as a base unit?

Overdrive wrote:

Tiran wrote:

If 13 Pahrtahvotee is really right than the time span is: 13 * 25 * 25 * 25 * 1.39285737931

Does that convert down into seconds as a base unit?

Yes, it's seconds as float but I made a typo. It's 13 * 25 * 25 * 5 * 1.39285737931s = 13 * 3125 * 1.39285737931s

factor seconds/prorahntee = 1.39285737931

_________________

[KI again #01792364]| Uru images | KI guide