Unidentified broadcast - 7/20/07

SkyBruin-ML

Wow nice conrac, I and a few others were struggling through that translation to ascii as well. your right the translation has been giving me fits, but what you came up with looks right with what we ended up with so far.

Since Strayshot seems to want everyone to work on this I'll continue with this here. I had decided to work with others from zion in secret but if strayshot doesn't mind I'll share.

the first data node listed was just outside of sai kung central hardline, most liekly on the vector instance, that is where coffinsnail had been seen before, either by the angels or if I remeber correctly outlaw54 mentioned him beening seen there.

As for the other locations Pamela showssets of data that we can possibly use to pointpoint the coordinates. I'll play around with it here on vector and if I figure anything out I'll post here.

**Conrac**

I have been looking at the Pamela Feed .. Seems the feed is updated every day with a new localization.

The first scene was at Sai Kung Central.

The second on the 20th Floor of the Kedemoth Tower that tisiphone calls home.

The third had poor signal reception and seems to be from under the Edgewater docks

Todays scene was in an apartment in Rogers Way near the broken down roadway and one of the Morpheus Beacon Sightings.

In order to make use of the Adelia tool we need to be able to reverse triangulate the locations of the data nodes.

This is a much harder problem then a normal forward triangulation. Consider that in the forward problem the the Target emits a signal at some time, call it T0. The signal propagates isometrically and is received at the Data nodes at some later times T1, T2 and T3. The data node locations are known locations. The data nodes are capable of determining the azimuth and elevation of the incoming signal. We are assuming straight line propagation, here. This direction is represented by a unit vector and for a given Node forms the parametric equation of a line. that is

XT= X1 + A1*t1, YT=Y1 + B1*t1, and ZT=Z1 + C1*t1

Where (XT,YT,ZT) are the Coordinates of the Target (in meters), (X1,Y1,Z1) are the coordinates of the Node (also in Meters) and (A1,B1,C1) are the components of the Unit Vector indicating the direction of the Target measured by the Data Node (these can be in meters or meters/second) depending on how one treats the variable t1 (the line parameter for node 1). T can either be dimensionless or expressed in seconds if one knows the propagation speed of the signal. The variable t takes on all values from 0 to infinity. It allows one to trace out all points that lie on the line at whatever resolution to user desires. There are equivalent equations for the other two nodes. All three nodes share the same target but different values for the direction Vector and the line parameter at the point of intersection. We are assumming perfect straight line propagation os only two Modes are required to provide an intersection by solving a set of simultaneous equations for the values of t1 and t2 at the point of intersection. t3 can be calculated for confirmation. that is

X1 + A1*t1 = X2 + A2*t2, Y1+B1*t1 = Y2 + B2*t2, Z1+C1*t1 = Z2+C2*t2

once t1, t2 and t3 are known they can be substituted into the parametric equations of any of the lines to give the coordinates of the Target.

Now consider what Pamela does for us .. First she provides us with the coordinates of the Target... presumably by performing the triangulaization I have described here. She also provides us with a direction vectors that shows us the direction from the target to each one of the nodes. What she does not provide us directly is the travel time for the signal from the target to each of the Nodes.. Therefore we have no direct way to calculate how far along the direction line the node is. What she does provide us with is a frequency of the outgoing signal from the target ... From which we must derive a distance and the query frequency used by the node because in order to retrieve the data with Adelia we must provide the location and the query frequency of the node. Presumably one can pull the data from each of the nodes used for triangulation.

When one looks at the Pamela data in more detail one realizes several things .. First the Direction vectors are not normalized, which is how one might arrive at a distance to the node. From the Sai Kung scene one can by inspection determine that the t parameter for the indicated node is exactly equal to 2. It also turns out that the outgoing freq from the target is exactly 18 times the Node frequency. In fact all the outgoing frequencies in the first scene are exactly divisble by 18. This includes the number in the upper right hand corner of the if one discards the last digit. I have tried playing around with frequency ratios for determining distance but have not had much success.

In the second scene the frequencies have a highest common denominator of 3. The direction components howver are very large which does not jive very well with the length of the node-target lines in the picture.

At the moment I do not know how to proceed .. perhaps a night sleep will provide me with some new ideas.

**PS10N** · 08/06/2007 19:56:59

As I stated in my logs, Conrac is the genius behind the progress. There are not enough congratulatory emotes in the interface to give you the props you deserve for this, Conrac. Between your brain work, my network and the Furious Angel's footwork (major props to all you e|ee+ Furious Angels too) we will have this solved yet. I'm calling in some more resources on the Zion Network, so more gray matter will be put to work on the location of more nodes. I'm working on some illustrations for those who aren't experts in 4D calculus reverse triangulation. Coordinate real-time at the following addresses:

http://www.smokytopia.com/mxo/
irc://irc.siradio.fm:6667/#siradio
ps10n (Yahoo Messenger, Xfire)
Ps10nMxO (AIM)
[email protected] (email)
[email protected] (Windows Live compatible, secondary email)

Contact me for Teamspeak details. PM me here on the forums if you'd like, tho it's the slowest Dropbox I use.

/\/\()|2|= +() (()/\/\|= $()()/\/ /\/\\| |=||_+|-|\| |_|++|_|= |>|6|()/\/$

There is no such thing as MxO for Dummies... not if you're paying attention.

**Darminian**

Most of that just seems way too beyond my comprehension, that being said if theres something im good at it's finding the location of random shots in mega city - so besides their existance - is there anything about this nodes that makes them different outside of their conjunction and relation to the joker, or are they just random nodes along the way?

Also - max props to Conrac.

Darminian

**GypsyJuggler**

Okay so I tried (376, -10, -151: 4.7832) and (4, 4, 603: 9.5936) in Adelia and got nothing so it looks like 't' might not be consistent either. EndGame seems to have complicated things though and now I'm stuck trying to figure out which set of coordinates from 6.50072 relates to the Sai Kung Special Node and how. That should give us some idea how these coordinates work across districts and hopefully give us a lead on working out where the other Nodes are. Personally I have the feeling there's one in each district (if you count Richland and Westview as a single district). The frequencies shouldn't have a bearing on locating the Nodes so long as we can find the right way to figure the supplied coordinates.

Oh, and if you go straight to Adelia or Pamela you get white on black rather than black on black.

**Darminian**

Having one in each counting richland and westview as one would make sense, especially with the recurring triangulation business.

Darminian

**broin** · 08/07/2007 10:25:19

Ahhhrrrgghhh...

Well I kind of figured this would happen. I have been at the Pamela Page since about 01/2007. Though the Pamela Page you all are seeing is not what was originally there... and the one that is being posted now has changed from what was displayed in June. There was an additional code and different x,y,z coordinates than what is up now. Suffice it to say it took me about 4 days to decode the ASCII script to get the HTMl Pamela Page and then from there we started working at finding the different locations of the nodes. Though when we had the Pamela Page originally there was just one picture, the top one, and the text at the top was different as well... Suggesting a different type of system for finding the nodes. A program was actually written by one of our members to locate the other nodes based off of XYZ coordinates and frequencies and we then inputed about 1000 + different locations in the Adelia page to find matches to them. Which there were none... Simply because the puzzle had not been completed.

From:Rarebit

To:broin

Date:02/02/2007 11:10:30

Subject:Re:Unidentified Broadcast Live Events Post

You are correct, the puzzle is currently incomplete.

I will talk to Strayshot about sharing the additional information that I have which is not now contained on the different pages. Hell, for all I know the xyz cords that I have that were posted in June were wrong and that's why they changed them to the new ones. However, I want to make it clear there are those who spent numerous numerous hours working on this puzzle. Not just FA memebers, but others in the community who were working with the original Scanline Crew and figuring things out. I do not like the idea of an individual having done so much work and dedicated so much time to a puzzle or storyline activity, only to have all of that hard work and information basically thrown out on the forums, for anyone to gather and run with. If in the end someone who has not put in the time or effort but is simply able to piggy-back on the hard work of others is granted some type of special item in game I find that extremley extremley disoncerting. Then again if like Strayshot says there is no bonus to coming across the finish line first then I'll be more than happy to share what I have.

**PS10N** · 08/07/2007 20:14:51

Broin, that was quite forthcoming. Thank you again. Rarebit, I really respect you for saying what you did back in February in that PM to Broin. Everything I've experienced in MxO shows that teamwork is the best way to accomplish goals. Indeed, the path of the One is made by Many, we stand on the backs of giants to achieve this view, it takes a lot of people to run a railroad and etc. Please stand comforted to know that some of us are not in this for the unique reward items. Healers, Buffers and Ressers will never get the "fatal shot," "most total damage," and "most single hit damage" rewards anyway. Could the ones who got the rewards have done it without the buffs, heals and res? The world may never know... but those of us who choose to support, do legwork and network to share information do it, not for a perpetual thing-ama-jig, but to be part of The Matrix' continuing story. Whoever is "first across the finish line" may well claim those honors, but s/he will have done it with the help of many others, which takes nothing away from each and every one of us who can say, "and I helped get us there!"

+ |-| [- /\/\ /-\ + |\ | }{ ( /-\ /\/ /\/ () + + [- |_ |_ \| () \_/ \/\/ |-| () \| () \_/ /-\ |\ [-
you should continue to press ctrl-a on sites which may contain hidden text. if you don't like what you are drinking, change fonts.

Attention Operatives: As of the afternoon of Tuesday, August 07, 1999 MCT, there is a new Image on the Scanline Receivers. I.E. Those of you with a History with Scanline images will know where to look for the address.

**PS10N** · 08/08/2007 00:29:52

Tefnut wrote:

Hidden text in the adelai site:

Top of page:

Node accessed.
Data not found.

Accessing error log.

8.25.17.37.26

Bottom of page:

So he wants to play rough, does he? You're probably the one who's been cutting the strings on our puppets too. Not the wisest course of action, ol' buddy, ol' pal.

Hidden text in the PAMELA site:

Top of page:

Aborting standby mode.
Initializing main routine.
Unarchiving system files.
Loading target from config. Re-acquiring target signal.
Re-establishing PAMELA network. This may take some time...

For assistance, type /helpdoc.
>> /helpdoc

Photovisual Adaptive Mapping Encrypted-Link Actuator is used to track data flow between nodes. Can operate in single-target tracking or sector-scanning modes. Broad spectrum frequency analysis enabled. Multiple data samples required for triangulation of single signal source/destination. Visual display provides three-dimension coordinate identification (X,Y,Z), parametric signal representation (X:,Y:,Z, and outbound signal frequency (freq).
I work well with my sister. Please use responsibly.

System Online.

Mid page:

Reformatting Output. One moment please.
Visuals Updated.

Launching Protocol "EndGame"...
"EndGame" Loaded.

Resolving...
"EndGame" Unloaded.

While it may not be officially "hidden", the text was in black. I thought t would help to post it here as well.

Great detective work. Some people are getting black on black text while others are getting white on black. Viewing the source code of the web page and/or the ctrl-a method work well. The numbers "8.25.17.37.26" and "8.25.17.38.13" are time stamps in the format. M.DD.HH.MM.SS (month, day, hour, minute, second) Scanline first came across CoffinNail, the Seeker Drone and Agent Wilson on that date last year in Sai Kung. Keep up the efforts to pull in pieces of the puzzle.

**PS10N**

The newest surveillance photo pertaining to this case has been analyzed. Results will be forthcoming after an appropriate period for oversight. Recommend operatives in possession of said photo use the following parameters for enhancements.

A) APS Software, topline menu
Image, Adjustments, Levels
Channel: RGB
Input Levels: 0 2.10 160
Output Levels: 0 255

Use the result as the basis for two different enhancements:

B) APS Software, topline menu

Filter, Video, De-interlace

Odd fields
Interpolated

OK

Note specifically the object in the upper right hand corner.

Use the result of step A for a second enhancement:

C) APS Software, topline menu

Filter, Video, De-interlace

Even fields
Interpolated

OK

The final enhancement is useful only where the interlace scanlines were not synchronous. Note the tube-like objects in square 6 if the grid is:

1|2|3
-+-+-
4|5|6
-+-+-
7|8|9

Results will be forthcoming after an appropriate period for oversight. Stay frosty everyone, it's getting hot out there.

.fawna.

hmm... no new posts?

**GypsyJuggler**

Okay I'll state where I'm up to explicitly. I think this is the state of progress but there might be people who have gotten further.

Node Location: 426, -14, -95 Sai Kung International - Freq 12.4937
Target Location: 833, 153, -970 Kedemoth Richland
Possible Vectors:
-449t, -38t, 48t - Freq 502.7070
292t, -66t, -41t - Freq 560.6091
278t, -157t, 504t - Freq 360.1716

One of those Vectors will describe the difference between the Node Location and the Target Location.
Anyone know which one?

**Conrac** · 08/09/2007 14:59:29

Well since we are advocating sharing .. I suppose I should share my failures along with my successes regardless if it
makes me look like a fool... Perhaps somebody will see the error in my logic..... Having said that ....

I am stuck at the same place ...

If I had to guess, I would select the bearing line with the freq of 560.6091.
It is the bearing line with the smallest magnitude of vector components (the closest node)
and the matrix characters under the frequency match the characters of the defined node in
the Sai Kung image.

Having said that, I have not come up with the relationship that will give the node location.

Let us consider what we are trying to do....

Variable definition for the first node/bearing line

    (XT,YT,ZT) - x,y,z coordinates of the target in meters. (Known)

    (X1,Y1,Z1) - x,y,z coordinates of the first node in meters (Unknown)

    (A1,B1,C1) - x,y,z coordinates of the direction (velocity?) vector (Known)
                         If this is just a direction then the units are meters and the
                         T parameter is just a scale factor. If this is a velocity then
                         the units are meters/(some time unit) be it seconds, milliseconds,
                         microseconds, nanoseconds or minutes of hours or even days. We
                         simply do not know what the time units in use are based on the
                         information in the Pamela feed.

    T1          - A dimensionless scale factor giving a distance multiple, or the
                     propagation time from Target to Node in some time unit. This depends
                     on how the vector (A1,B1,C1) is interpreted. For most bearing lines
                 this is an Unknown. In the Sai Kung image we are given that
                     this parameter is equal to 2. Presumably we will be able to arrive
                     at a method for determining the value of T for each of the bearing
                     lines in the best case, in the worst case maybe only one bearing line
   per scene will work. (Unknown)

    V1          - Magnitude of the direction (velocity?) vector ( Known - derivable )

    FT1        - Target Outgoing frequency (N-cycles/some time unit) (Known)

    FN1        - Node Outgoing frequency (N-cycles/some time unit) (Unknown)

    K           - The Key (the number in the upper right hand corner of the screen)

By substituting a 2 for the 1 in each of these definitions we arrive at the set of variables defining
the second node/bearing line and likewise substituting a 3 for the 1 in each of these equations
would supply the set of variables for the third node/bearing line. Please note that in the general
case the nodes all lie at different distances from the Target so that the propagation time from
target to node (T1,T2,T3) would expected to be different for each line. However depending on how
the Direction(Velocity) Vector is defined it could be T1=T2=T3. We just dont know what is the case.

Therefore the set of equations defining the location of the data nodes for three bearing lines are
in the general case:

   X1=XT+A1*T1       Y1=YT+B1*T1     Z1=YT+C1*T1     V1 = Sqrt(A1**2+B1**2+C1**2)
   X2=XT+A2*T2       Y2=YT+B2*T2     Z2=YT+C2*T2     V2 = Sqrt(A2**2+B2**2+C2**2)
   X3=XT+A3*T3       Y3=YT+B3*T3     Z3=YT+C3*T3     V3 = Sqrt(A3**2+B3**2+C3**2)

Since each equation involves two unique unknowns (i.e for a single vector component a set of three
equations in six unknows) we can not reduce them to solve for the locations of each of the data nodes.

Even in the special case where we assume T1=T2=T3 and therefore the Direction(Velocity) vector
contains information on relative node distances the equations are simplified to three equations
in four unknowns for a single vector component which still won't allow us to find the exact node locations.

So we need to come up with a fourth equation that will give us the T parameter for a given
bearing line. Whatever theory we come up with must provide a T=2 and FN1=12.4937 when applied
to the known node location in the Sai Kung image.

This brings us to the Outgoing Frequency provided for each of the bearing lines. Some talk has been
advanced that by inverting the frequency one can arrive at a time. This is true .. but the problem is
this time does not relate to the distance the signal of that frequency propagates but rather the the
amount of time the signal takes to go through a complete cycle.

Let me explain.

The usual unit of frequency is a Hertz AKA cycles/second and the various mutliples of this KiloHertz
(thousand cycles/second), Megahetz (million cycles/second) or GigaHertz (billion cycles/second) to name
some common ones.

A signal carrier can be thought of as a sine curve that endlessly repeats. One cycle is defined as the time
the carrier takes to repeat itself .. I.E in the case of a sine curve, one 2pi advancement of the curve. Now
imagine a particle (a photon in the case of classical E-M radiation theory) that follows this curve. It has
some velocity. The distance that the photon travels in one cycle (known as a wavelength) can simply be
determined by dividing the particle velocity (m/sec) by frequency (cycles/sec) to arrive at the wavelength
in (meters/cycle). This is the distance the signal moves in a single cycle. The higher the frequency the
shorter the wavelength. Now here is the rub.... in the case of electromagnetic radiation in a vacuum all frequencies
move at the same speed, the speed of light. The medium is called non-dispersive as the velocity of propagation is
independent of frequency. Indeed in the case of EM radiation most media to a very good approximation are
non-dispersive. So knowing the frequency of a signal does not tell us anything about the propagation speed and
hence by itself can not provide a distance to a target. If however, we independently knew the propagation speed
and knew the number of wavelengths contained between the target and the receiver we might be on to something.

In the Sai Kung image I pointed out that the ratio of the target frequency to the node frequency is exactly
18. It also turned out that the other bearing line frequencies were also exactly divisible by 18.
If you multiple each of the frequencies by 10000 to make them integers and then factor them you will find that
18 is the largest common factor in the three bearing line target frequencies. It is also true that if you drop the last digit
from the key value in the upper right hand corner and multiply that by 10000 and it also has a factor of 18.
Coincidence .. maybe .. in general I don't believe in them.

In the Kedemoth all the frequencies (including the modified key) have a largest common denominator of 3.

The Edgewater data has a largest common denominator of 9 and the Roger's Way scene has a factor of 2 in common.

Now for the time. Interestingly if you divide the largest common denominator by the key code in the Sai Kung image
you come up with a value of 2.0872 ... this is pretty close to the T=2 parameter supplied to us. The thing is I
had already had assumed T=2 for the other bearing lines and applied the frequency ratio of 18 in the data set and
did not end up with any other Adelia data extractions. So .. this may mean only one node per scene will produce data or
that I am barking up the wrong tree. Indeed when you think about it the ratio does not give us the total number of cycles
between target and node, only that the higher frequency has 18 times as many cycles as the lower frequency.

Thats my thinking so far .. It generated the following set of numbers with only the first one producing
the Adelia output we already knew about.

Node X    Node Y    Node Z    Freq
426   -14             -95      12.4937
374   -6           -119      4.7832
-14   9            667    9.5936
968          123   -989    186.8697
1040      135   -948    167.569
961      81   -737    120.0572
-545    -18    -1090 660.2566
-837 5           -215    401.3625
-535      14           -577    228.4389
-242 9   -353 388.9438

Anybody else have a theory ?

A perplexed,

Con

**PS10N**

Thanks for the left-brain analysis, Conrac. I'll pass it on to other math genii I know.
As for the right-brain analysis, here it is, as promised.

Enhancements of Scanline Surveillance Photo

**GypsyJuggler** · 08/09/2007 21:24:44

So at some point I realised that instead of staring blankly at the numbers until they made sense I should hit them with some old school algebra and see if that helped. It didn't but here's what I got anyway. The answers are all to six decimal places except for the two containing brackets to show repeating digits.

426-449t=833 -> t=-0.906459

-14-38t=153 -> t=-4.394737

-95+48t=-970 -> t=-18.2291(6)

426+292t=833 -> t=1.393836

-14-66t=153 -> t=-2.5(30)

-95-41t=-970 -> t=20.121951

426+278t=833 -> t=1.464029

-14-157t=153 -> t=-1.063694

-95+504t=-970 -> t=-1.636905

So then I went and took a closer look at the codes attached to the vectors and sure enough the 560.6091 (Ked) does match with the 224.8866 (Sai). When I checked the rest of the images, however, I found that the codes from Sai Kung are only repeated in Kedemoth. Edgewater and Roger's Way show almost entirely different codes suggesting that the system differs between east and west in some way. Off the top of my head I'd suggest using the frequencies from Kedemoth and Sai Kung as a measure of distance which would give us two possible locations for each Node but the obvious problem with that is how to measure distance across districts.

Back to the drawing board I guess.

Edit: Typo.