All of the above related to Gametap MOUL, and Andreas Jurenda's NegilahnPortalCalculator still serves us well today in MOULagain ref
http://members.chello.at/andreas.jurenda/moul/negilahnportalcalculator.htm , and I found myself revisiting old haunts and attempting to add or refine the old puzzles and solutions afresh. I didn't find a post of the following so thought it belongs here. For simplicity I'm focussing on Portal Times.
There is D'ni Time (Clock), Teledahn Time (?)(Barron's Office Chart), and Pod Time (Museum Chart): Times can indeed be related, but we are only interested in the Pod Time here for now. You need to know your D'ni Numbers (I use the ones printed all over the Bevin Classroom Floor), and Each Pod ID number, (go visit and look), to figure the Clues. Empirical evidence has already establishes the key information namely: Negilahn sky records (this thread) indicate a Pod day/night cycle of 15:43:04.83 hrs:mins:secs , of Earth Time, which appears to have served us well. And an examination of the Museum Chart shows the Pod day/night cycle to be 13 Units of Pod Time.
The following constitutes a rational approach with two slightly differing solutions for any single explorer's consideration, comment and/or correction. The fundemental assumption here is that Cyan would have selected practical rounded numbers to crunch. Dunno. Since some questions still remain, here is the conventional warning.
Further examination of the Museum Chart allows us to identify and locate each Pod on the Museum Chart's Time Zones. This now tells us the Pod order in which a common event will appear in each Pod, if we trust the artistic licence which indicates that a single sun moves from West to East (we can always confirm it later). And by taking a PrtScrn Screenshot and pasteing it into Word, say, and printing it, you can take a Millimeter scale and ratio the Pod Locations shown to get a better Pod Time Zone absolute location. From this you can roughly figure the relative Time delays between each Pod. Now we know the approximate Pod Time intervals and order, and we know the same intervals in Earth Hours (ref above, 15:43:04.83 hrs:mins:secs/13 Pod Time Units = 1.209078 Earth Hrs/Pod Time Units) we only need to know
one Pod's actual Portal time and we can create our own short or long-term table of furure Portal Event Times. That one (easiest) Pod is Payiferen, if we have cought a glimpse of the Sun beams through the window there and guessed what they might do. Payiferen observation also shows that at High Noon the Sun is very slightly off center of the Pod, which indicates that the Sun actually moves across the Museum Pod Chart equator, not the arrowed lines shown below there.
Following this approach I came up with numbers which seemed to correllate pretty well, and with remarkably small percentage error after rounding out as follows
1) Least error rounding assumptions: Negilahn/Dereno/Payiferen/Tetsonot/Negilahn Intervals are 0 Units(Baseline)/1 Pod Time Unit/0.5 Earth Hours/3 Earth Hours/11 Earth Hours, respectively. If Cyan intended this solution it's extraordinarily cunning; because it allows us to calculate an Earth Hours of a day/night cycle independantly of any other observations just by adding up the numbers of mixed units with a variable constant, namely Y= (14.5 Earth Hours/(13-1) Pod Units) = 1.2083(3recurring) or 1:12:30 (exact) hrs:mins:secs per Pod Time Unit. Problem is, its smaller than the number Jurenda appears to use (1.209078) to sustain his long term record. Day/Night Cycle comes out to be 15:42:30 (exact) hrs:mins:secs. But this still might be OK....see below
2) The next best min error rounding assumptions: Negilahn/Dereno/Payiferen/Tetsonot/Negilahn Intervals are 0 Units(Baseline)/1 Pod Time Unit/0.5 Pod Time Units/2.5 Pod Time Units/9 Pod Time Units, respectively. This solution accepts any rate you want to use, but assumed one unusually large error in Dereno/Payiferen interval. It is a less likely solution IMHO.
Problem is, that everybody experiences the Portal arrival across a wide tolerance, as the server selects a sequence of affected Avies and nobody can say when the server actually sends out the first Portal command. In short, theres a lot of noise in the process. Jurenda has to use numbers which keep calculating accurately or he has to automate his own Avie experience occasionally to measure Portal creep and reset it. If so, its possible that Solution 1) may be an advance; I can't tell, yet. But I thought I ought post it and see what others think....theres always other ideas...
(Edit) OH !! I forgot ! The intriguing thing about Pod Portal Times is that it should be possible to calculate those occasional times
when a Portal arrival will coincide with a D'ni Clock time which correlates to that Pod's D'ni Number ID. I found one once, but never tried to run the numbers yet.. Such Grand Conjunctions ought to be advertized and treated with Great Celebration in MOUL, I respectfully submit. So the Challenge is herebye declared to all, the Vision is defined, and maybe Andreas Jurenda will compete for the solution too ?....

..........And I hope it will be posted here..
_________________
Abjab
Hi All !!.....Myst'ya !.....
