1 June - The A Sign in Space Message
After carefully documenting all their work, a team of participants announce their very compelling message candidate. This is the data that was transmitted from TGO using memory dump commands.
Link to Discord: https://discordapp.com/channels/1066055437457297469/1110258624950968421/1113643107632828438
Link to the A Sign in Space Message: https://github.com/BatchDrake/ASignInSpace/blob/master/Candidates/artifacts/data17.bin
31 of May - The headers in TGO's space packets use an ESA protocol called PUS
One participant has found that the headers in TGO's space packets, which were mostly overlooked before, use an ESA protocol called PUS. These headers tell us something about the meaning of each packet: its purpose, and the kind of data it contains. With this new information, the participants quickly uncover the meaning of each of the packet "types" (APIDs) that appeared when the message reception began. APID 0017, which was considered as the main candidate for containing the message is seen to contain "memory dumps" from the spacecraft. The other APIDs contain information about the commands that the spacecraft executed to generate the memory dumps.
Link: https://discord.com/channels/1066055437457297469/1110258553689739276/1113193510590480465
30 of May - Conversation still revolves around the "star-map"
A large part of the conversation still revolves around the "star-map".
Could it be pulsars? Active galactic nuclei? Molecular clouds? Maybe it is related to TGO's star tracker? These are cameras on the spacecraft
that look at the stars to find how the spacecraft is oriented. In parallel, there are attempts to visualize the same data in a completely
different way.
Link: https://discord.com/channels/1066055437457297469/1112472708471603221/1112907480142446662
29 of May - What is this?
The participants continue to analyze the data in the three APIDs ("packet types") which are considered the most likely to contain the message. One of the three APIDs (the one numbered as 0x17) has received the most attention.
Link: https://discordapp.com/channels/1066055437457297469/1110258553689739276/1112697484741972039
28 of May - Decoding state of the art
On Discord, Daniel Estévez summarized the decoding process state of the art.
Link to the post: https://discordapp.com/channels/1066055437457297469/1110258553689739276/1112487058326437960
28 of May - Data missing check
Noticing that part of the data was missing from earlier decoding attempts, the participants make some improvements to their approach and decode again the Green Bank Telescope SigMF recording. Now they carefully check the frame sequence numbers and CRCs to ensure that no data has been lost or corrupted.
Link: https://discordapp.com/channels/1066055437457297469/1110258553689739276/1112163314110320700
27 of May - Studying the data in the space packets from different points of view
The participants are studying the data in the space packets from different points of view. They try to find patterns, and plot the data in different ways. Some of the participants are still working on the earlier stages of the decoding process, with the SigMF recordings. They want to manage to decode them on their own to understand how this can be done. Other participants help them set up the software to do this.
Link: https://discordapp.com/channels/1066055437457297469/1110258553689739276/1111409212069785600
26 of May - Identified the CCSDS protocols used by TGO
The organizers have hinted that the message is in the telemetry signal of TGO, intermixed with other data that is sent normally by the spacecraft.
Link: https://discordapp.com/channels/1066055437457297469/1110258553689739276/1111682614361870346
25 of May - The SigMF recordings are available for download
The SigMF recordings made at the Allen Telescope Array, Green Bank Telescope and Medicina Observatory have been made available for
download.
The participants have explored these recordings using different software. Link: https://discordapp.com/channels/1066055437457297469/1110258553689739276/1111030391613181962