Skip to content

Commit 64810a2

Browse files
authored
Add intergalactic-transmission exercise (#1039)
1 parent b3b4ef1 commit 64810a2

9 files changed

Lines changed: 744 additions & 0 deletions

File tree

bin/auto-sync.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,7 @@ hamming
3737
hello-world
3838
high-scores
3939
house
40+
intergalactic-transmission
4041
isbn-verifier
4142
isogram
4243
killer-sudoku-helper

config.json

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -847,6 +847,14 @@
847847
"prerequisites": [],
848848
"difficulty": 3
849849
},
850+
{
851+
"slug": "intergalactic-transmission",
852+
"name": "Intergalactic Transmission",
853+
"uuid": "1e91fd0f-98ee-404c-ac69-fc6a012f6c1b",
854+
"practices": [],
855+
"prerequisites": [],
856+
"difficulty": 3
857+
},
850858
{
851859
"slug": "kindergarten-garden",
852860
"name": "Kindergarten Garden",
Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
# Instructions
2+
3+
Your job is to help implement
4+
5+
- the transmitter, which calculates the transmission sequence, and
6+
- the receiver, which decodes it.
7+
8+
A parity bit is simple way of detecting transmission errors.
9+
The transmitters and receivers can only transmit and receive _exactly_ eight bits at a time (including the parity bit).
10+
The parity bit is set so that there is an _even_ number of 1 bits in each transmission, and the parity bit is always the first bit from the right.
11+
So if the receiver receives `11000001`, `01110101` or `01000000` (i.e. a transmission with an odd number of 1 bits), it knows there is an error.
12+
13+
However, messages are rarely this short, and need to be transmitted in a sequence when they are longer.
14+
15+
For example, consider the message `11000000 00000001 11000000 11011110` (or `C0 01 C0 DE` in hex).
16+
17+
Since each transmission contains exactly eight bits, it can only contain seven bits of data and the parity bit.
18+
A parity bit must then be inserted after every seven bits of data:
19+
20+
```text
21+
11000000 00000001 11000000 11011110
22+
↑ ↑ ↑ ↑ (7th bits)
23+
```
24+
25+
The transmission sequence for this message looks like this:
26+
27+
```text
28+
1100000_ 0000000_ 0111000_ 0001101_ 1110
29+
↑ ↑ ↑ ↑ (parity bits)
30+
```
31+
32+
The data in the first transmission in the sequence (`1100000`) has two 1 bits (an even number), so the parity bit is 0.
33+
The first transmission becomes `11000000` (or `C0` in hex).
34+
35+
The data in the next transmission (`0000000`) has zero 1 bits (an even number again), so the parity bit is 0 again.
36+
The second transmission thus becomes `00000000` (or `00` in hex).
37+
38+
The data for the next two transmissions (`0111000` and `0001101`) have three 1 bits.
39+
Their parity bits are set to 1 so that they have an even number of 1 bits in the transmission.
40+
They are transmitted as `01110001` and `00011011` (or `71` and `1B` in hex).
41+
42+
The last transmission (`1110`) has only four bits of data.
43+
Since exactly eight bits are transmitted at a time and the parity bit is the rightmost bit, three 0 bits and then the parity bit are added to make up eight bits.
44+
It now looks like this (where `_` is the parity bit):
45+
46+
```text
47+
1110 000_
48+
↑↑↑ (added 0 bits)
49+
```
50+
51+
There is an odd number of 1 bits again, so the parity bit is 1.
52+
The last transmission in the sequence becomes `11100001` (or `E1` in hex).
53+
54+
The entire transmission sequence for this message is `11000000 00000000 01110001 00011011 11100001` (or `C0 00 71 1B E1` in hex).
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Introduction
2+
3+
Trillions upon trillions of messages zip between Earth and neighboring galaxies every millisecond.
4+
But transmitting over such long distances is tricky.
5+
Pesky solar flares, temporal distortions, stray forces, and even the flap of a space butterfly's wing can cause a random bit to change during transmission.
6+
7+
Now imagine the consequences:
8+
9+
- Crashing the Intergalactic Share Market when "buy low" turns to "sell now".
10+
- Losing contact with the Kepler Whirl system when "save new worm hole" becomes "cave new worm hole".
11+
- Or plunging the universe into existential horror by replacing a cowboy emoji 🤠 with a clown emoji 🤡.
12+
13+
Detecting corrupted messages isn't just important — it's critical.
14+
The receiver _must_ know when something has gone wrong before disaster strikes.
15+
16+
But how?
17+
Scientists and engineers from across the universe have been battling this problem for eons.
18+
Entire cosmic AI superclusters churn through the data.
19+
And then, one day, a legend resurfaces — an ancient, powerful method, whispered in debugging forums, muttered by engineers who've seen too much...
20+
21+
The Parity Bit!
22+
23+
A method so simple, so powerful, that it might just save interstellar communication.
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
{
2+
"authors": [
3+
"resu-xuniL"
4+
],
5+
"files": {
6+
"solution": [
7+
"IntergalacticTransmission.php"
8+
],
9+
"test": [
10+
"IntergalacticTransmissionTest.php"
11+
],
12+
"example": [
13+
".meta/example.php"
14+
]
15+
},
16+
"blurb": "Add parity bits to a message for transmission",
17+
"source": "Kah Goh",
18+
"source_url": "https://github.com/exercism/problem-specifications/pull/2543"
19+
}
Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
<?php
2+
3+
declare(strict_types=1);
4+
5+
function transmitSequence(array $sequence): array
6+
{
7+
return array_map(
8+
fn ($eightBit) => sprintf('0x%02x', bindec($eightBit)),
9+
array_map(
10+
function ($sevenBit) {
11+
$sevenBit = str_pad($sevenBit, 7, '0');
12+
substr_count($sevenBit, "1") % 2 === 0 ? $parityBit = "0" : $parityBit = "1";
13+
return $sevenBit . $parityBit;
14+
},
15+
str_split(
16+
implode(
17+
'',
18+
array_map(
19+
fn ($hex) => sprintf('%08b', hexdec($hex)),
20+
$sequence
21+
)
22+
),
23+
7
24+
)
25+
)
26+
);
27+
}
28+
29+
function decodeMessage(array $message): array
30+
{
31+
return array_map(
32+
fn ($eightBit) => sprintf('0x%02x', bindec($eightBit)),
33+
array_filter(
34+
str_split(
35+
implode(
36+
'',
37+
array_map(
38+
function ($eightBit) {
39+
if (substr_count($eightBit, "1") % 2 === 0) {
40+
return substr($eightBit, 0, 7);
41+
} else {
42+
throw new Exception("Error: wrong parity");
43+
}
44+
},
45+
array_map(
46+
fn ($hex) => sprintf('%08b', hexdec($hex)),
47+
$message
48+
)
49+
)
50+
),
51+
8
52+
),
53+
function ($eightBit) {
54+
return strlen($eightBit) === 8;
55+
}
56+
)
57+
);
58+
}
Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
1+
# This is an auto-generated file.
2+
#
3+
# Regenerating this file via `configlet sync` will:
4+
# - Recreate every `description` key/value pair
5+
# - Recreate every `reimplements` key/value pair, where they exist in problem-specifications
6+
# - Remove any `include = true` key/value pair (an omitted `include` key implies inclusion)
7+
# - Preserve any other key/value pair
8+
#
9+
# As user-added comments (using the # character) will be removed when this file
10+
# is regenerated, comments can be added via a `comment` key.
11+
12+
[f99d4046-b429-4582-9324-f0bcac7ab51c]
13+
description = "calculate transmit sequences -> empty message"
14+
15+
[ee27ea2d-8999-4f23-9275-8f6879545f86]
16+
description = "calculate transmit sequences -> 0x00 is transmitted as 0x0000"
17+
18+
[97f27f98-8020-402d-be85-f21ba54a6df0]
19+
description = "calculate transmit sequences -> 0x02 is transmitted as 0x0300"
20+
21+
[24712fb9-0336-4e2f-835e-d2350f29c420]
22+
description = "calculate transmit sequences -> 0x06 is transmitted as 0x0600"
23+
24+
[7630b5a9-dba1-4178-b2a0-4a376f7414e0]
25+
description = "calculate transmit sequences -> 0x05 is transmitted as 0x0581"
26+
27+
[ab4fe80b-ef8e-4a99-b4fb-001937af415d]
28+
description = "calculate transmit sequences -> 0x29 is transmitted as 0x2881"
29+
30+
[4e200d84-593b-4449-b7c0-4de1b6a0955e]
31+
description = "calculate transmit sequences -> 0xc001c0de is transmitted as 0xc000711be1"
32+
33+
[fbc537e9-6b21-4f4a-8c2b-9cf9b702a9b7]
34+
description = "calculate transmit sequences -> six byte message"
35+
36+
[d5b75adf-b5fc-4f77-b4ab-77653e30f07c]
37+
description = "calculate transmit sequences -> seven byte message"
38+
39+
[6d8b297b-da1d-435e-bcd7-55fbb1400e73]
40+
description = "calculate transmit sequences -> eight byte message"
41+
42+
[54a0642a-d5aa-490c-be89-8e171a0cab6f]
43+
description = "calculate transmit sequences -> twenty byte message"
44+
45+
[9a8084dd-3336-474c-90cb-8a852524604d]
46+
description = "decode received messages -> empty message"
47+
48+
[879af739-0094-4736-9127-bd441b1ddbbf]
49+
description = "decode received messages -> zero message"
50+
51+
[7a89eeef-96c5-4329-a246-ec181a8e959a]
52+
description = "decode received messages -> 0x0300 is decoded to 0x02"
53+
54+
[3e515af7-8b62-417f-960c-3454bca7f806]
55+
description = "decode received messages -> 0x0581 is decoded to 0x05"
56+
57+
[a1b4a3f7-9f05-4b7a-b86e-d7c6fc3f16a9]
58+
description = "decode received messages -> 0x2881 is decoded to 0x29"
59+
60+
[2e99d617-4c91-4ad5-9217-e4b2447d6e4a]
61+
description = "decode received messages -> first byte has wrong parity"
62+
63+
[507e212d-3dae-42e8-88b4-2223838ff8d2]
64+
description = "decode received messages -> second byte has wrong parity"
65+
66+
[b985692e-6338-46c7-8cea-bc38996d4dfd]
67+
description = "decode received messages -> 0xcf4b00 is decoded to 0xce94"
68+
69+
[7a1f4d48-696d-4679-917c-21b7da3ff3fd]
70+
description = "decode received messages -> 0xe2566500 is decoded to 0xe2ad90"
71+
72+
[467549dc-a558-443b-80c5-ff3d4eb305d4]
73+
description = "decode received messages -> six byte message"
74+
75+
[1f3be5fb-093a-4661-9951-c1c4781c71ea]
76+
description = "decode received messages -> seven byte message"
77+
78+
[6065b8b3-9dcd-45c9-918c-b427cfdb28c1]
79+
description = "decode received messages -> last byte has wrong parity"
80+
81+
[98af97b7-9cca-4c4c-9de3-f70e227a4cb1]
82+
description = "decode received messages -> eight byte message"
83+
84+
[aa7d4785-2bb9-43a4-a38a-203325c464fb]
85+
description = "decode received messages -> twenty byte message"
86+
87+
[4c86e034-b066-42ac-8497-48f9bc1723c1]
88+
description = "decode received messages -> wrong parity on 16th byte"
Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
<?php
2+
3+
/*
4+
* By adding type hints and enabling strict type checking, code can become
5+
* easier to read, self-documenting and reduce the number of potential bugs.
6+
* By default, type declarations are non-strict, which means they will attempt
7+
* to change the original type to match the type specified by the
8+
* type-declaration.
9+
*
10+
* In other words, if you pass a string to a function requiring a float,
11+
* it will attempt to convert the string value to a float.
12+
*
13+
* To enable strict mode, a single declare directive must be placed at the top
14+
* of the file.
15+
* This means that the strictness of typing is configured on a per-file basis.
16+
* This directive not only affects the type declarations of parameters, but also
17+
* a function's return type.
18+
*
19+
* For more info review the Concept on strict type checking in the PHP track
20+
* <link>.
21+
*
22+
* To disable strict typing, comment out the directive below.
23+
*/
24+
25+
declare(strict_types=1);
26+
27+
function transmitSequence(array $sequence): array
28+
{
29+
throw new \BadFunctionCallException(sprintf('Implement the %s function', __FUNCTION__));
30+
}
31+
32+
function decodeMessage(array $message): array
33+
{
34+
throw new \BadFunctionCallException(sprintf('Implement the %s function', __FUNCTION__));
35+
}

0 commit comments

Comments
 (0)