Rendlesham Forest incident - Britian's Roswell

[Lee]

The new book 'Encounter at Rendlesham' is out received a copy yesterday.
At last it has full details of the binary code. Lat and long of the all the coordinates and photocopies of the last remaining pages of the note book. They've still clung to the ludicrous assertion that the first and last are Hy Brazil.

I'd like to see the full binary code too. Might have to get a copy of the book.

We had some good analysis in the old OMF thread, shame it's not available online anymore.

[Longeyes]

It occurs to me there is an error in the coding of the geolocation information here. There is nothing within the photos of Penniston's notebook to indicate the location of the decimal points in the coding. As presented here all locations have six decimal precision, except the one imputed to be HyBrazil, it has seven digits. Having been trained as a map maker and my knowledge of planetary mapping, one would not mix six and seven digit precision: 52.0942532 does not belong as a correct number, or all the other six decimal locations are not correct. Using seven digit decimals makes the origin and first set of numbers come directly to city hall in Woodbridge which leads me to suspect that seven digits are correctly the ones to use. But if seven digits should be used, that throws all locations int question. I really need to see photos of all of Penniston's notebook.

Agreed standard notation esp a machine would always give the same number of decimal figures.
I will copy them out this weekend
That's why we always needed them the interpretation of them is not correct or as exact as is made out.

[majicbar]

Agreed standard notation esp a machine would always give the same number of decimal figures.
I will copy them out this weekend
That's why we always needed them the interpretation of them is not correct or as exact as is made out.

It is an interesting exercise as one with knowledge of computer design to see the raw code that precedes machine code. What we see in Penniston's binary code is something that will be taken by the computer and loaded into machine registers and then processed from that point on. In order to make code work for longitude it would have to be loaded in registers with as I contend 7 digits and the remainder would be the degree coding, this is the only way to get 3 degrees, 30 degrees and 175 degrees to not confuse the computer, and by going to planetary notation the East West is negated and no other notation is needed as 359 degrees longitude would load just as well as any other degree of longitude, only needing three numbers, where 179E or 179W would require four. The machines design would be interesting to think about in comparison to how today's drones are handling geocoding, I suppose that would be considered a military secret, but perhaps it is out there as someone's dissertation for a degree, or in an expired patent.

[Longeyes]

Page 1 of note book
0100011001001110101010
10101010010010101
000100100001000011
01001111010011110100
01000100100101001
11(0)0100000101010100
0100010101000011010
011110100111001010
1000100100101001110
010101(0)10100111101010
100010101010101000
1010101110
01000011011000101
010100000101001
0_0100001001000
10101000110010011
1101010010

The underscore is a definate space. The numbers in brackets are where the characters are unclear.

[Longeyes]

Page 2
01000101_0101100(0)
01010000_01001100
0100111101010010
010000001010101000
1001001010011110100
1110_0100111101000
111_01001000_010101
010100110101000001
01001110_01001001
01010100_01011001
0011011_0011011
0011011_00111000
00110001_00110000
00110000

Again spaces are in the note book. Interesting that they start to group into 8's. 01 at the start of an 8 bit is the start of a capital letter. So you can begin to read the binary code. Putting in down like this enables us to see mistakes where they were made.

[Longeyes]

Page 3
0011010100110010
00110000001110010011
0100001100100011
0101001100110011
0010_01001110
001100010011001100
11000100110011
00110001001100100011
0110_00111011_0101
0111_010000110100
1111_0_1001110
01010100_0100
100100101001110

[Doc]

Nice work, Longeyes!

[calikid]

I'll probably process the code myself later when I have a scientific calculator (and spare time) handy.
Meanwhile can anyone tell me, are the numbers straight up binary?
Or are they also run thru an ASCII table conversion?
Parity bit (Error correction) present?

[Garuda]

I'll probably process the code myself later when I have a scientific calculator (and spare time) handy.
Meanwhile can anyone tell me, are the numbers straight up binary?
Or are they also run thru an ASCII table conversion?
Parity bit (Error correction) present?

There actually was a whole discussion about that, back at OMF, after it was pointed out that at the time this happened, 8 bit bytes weren't really used yet. Still, the whole sequence only makes sense if read as 8bit ASCII.

[Longeyes]

They are almost certainly 8 bit binary ASCII as they most match incredibly well. The binary contains errors though.
These pages are already on the net but thought out of consistency should do the whole load.