I disagree, I did some calculations just now, and it looks to me to be a bit sooner.
The countdown runs through 5000 points every 15 seconds, or thereabouts.
So the timer read exactly 17500000 at 11:35AM central time, meaning the timer would run out 14 hours and 30 minutes from then or at 3:05AM Tuesday morning...
17500000/5000 * 15 /60/60 =14.5hrs
Anyone else wanna try?
Woohoo, 14th person to solve the 4D rubik's cube...ever! http://www.superliminal.com/cube/cube.htm
Watch me solve a regular cube in 24.2 seconds at www.rubiks.dk videolist, Daniel Hayes!
As crazy as this may sound....it appears to be accelerating, so any calculation you do could be off because its gradually getting faster? Saturday morning around 9am it was at 61xxxxx, and Sunday around lunch time it was at 57xxxxx, so around 10xxxxx per 24 hours right? Wrong
One of the girls in my office just put it at Tuesday afternoon, but I have a sneaking suspicion it might be available late tonight somtime....
Nforce 2 Mobo-oem stock
Athlon Xp3000-Stock
768 mgs PC2100 @ 2.5/3/3
Radeon 9700 PRO/365/342
Western Digital 8mg cache ATA-133/160G/7200 HD
Win XP Home SP1
19" KDS "Extreme Flat"
Laptop
Athlon 64 3200+
512mg Ram
Mobile Radeon 9600
80G Hard Drive
so at 11:35, that's my best guess at how long it had to run placing the release time at:
01:01:57.3 AM Central time...
So if anyone knows what time zone www.madonion.com is run from, that might make sense. If they are on mountain time, that's almost exactly midnight tonight But I could be wrong I just did quick sloppy calculations and not so good measurements.
Yes, I was that bored.
Woohoo, 14th person to solve the 4D rubik's cube...ever! http://www.superliminal.com/cube/cube.htm
Watch me solve a regular cube in 24.2 seconds at www.rubiks.dk videolist, Daniel Hayes!
I found an entire website about that... I think the unofficial but commonly accepted term for the time derivative of acceleration is "jolt" or "jerk" or something to that effect, i'll see if I can dig it up.
I guess Ill get up at 2Am EST and start the dl. With the Internet traffic being less(hopefully) that time of night maybe the mirrors wont be overloaded, but my bet is that it will be days before Ill be able to get it through on a dial up....
Nforce 2 Mobo-oem stock
Athlon Xp3000-Stock
768 mgs PC2100 @ 2.5/3/3
Radeon 9700 PRO/365/342
Western Digital 8mg cache ATA-133/160G/7200 HD
Win XP Home SP1
19" KDS "Extreme Flat"
Laptop
Athlon 64 3200+
512mg Ram
Mobile Radeon 9600
80G Hard Drive
I was using my rubik's cube timer to time the intervals, I forgot that it counts down for 10 seconds before it starts counting back up... so all of my intervals should have 10 added to them...
new estimate is (using the same formula as before)
23 hours 24 minutes and 20.7 seconds after 11:35 AM CT Feb 10
or almost exactly 11:00AM CT Feb 11 Which is 12:00PM ET... I did take into account acceleration which may or may not be a product of errors in the measurement. But this is much much closer to what others have calculated.
Please accept my appologies for the mix up!
Woohoo, 14th person to solve the 4D rubik's cube...ever! http://www.superliminal.com/cube/cube.htm
Watch me solve a regular cube in 24.2 seconds at www.rubiks.dk videolist, Daniel Hayes!
Bookmarks