this post was submitted on 10 Oct 2023
163 points (93.1% liked)

Cool Guides

4676 readers
1 users here now

Rules for Posting Guides on Our Community

1. Defining a Guide Guides are comprehensive reference materials, how-tos, or comparison tables. A guide must be well-organized both in content and layout. Information should be easily accessible without unnecessary navigation. Guides can include flowcharts, step-by-step instructions, or visual references that compare different elements side by side.

2. Infographic Guidelines Infographics are permitted if they are educational and informative. They should aim to convey complex information visually and clearly. However, infographics that primarily serve as visual essays without structured guidance will be subject to removal.

3. Grey Area Moderators may use discretion when deciding to remove posts. If in doubt, message us or use downvotes for content you find inappropriate.

4. Source Attribution If you know the original source of a guide, share it in the comments to credit the creators.

5. Diverse Content To keep our community engaging, avoid saturating the feed with similar topics. Excessive posts on a single topic may be moderated to maintain diversity.

6. Verify in Comments Always check the comments for additional insights or corrections. Moderators rely on community expertise for accuracy.

Community Guidelines

By following these rules, we can maintain a diverse and informative community. If you have any questions or concerns, feel free to reach out to the moderators. Thank you for contributing responsibly!

founded 1 year ago
MODERATORS
 
top 20 comments
sorted by: hot top controversial new old
[–] ICastFist@programming.dev 24 points 1 year ago (2 children)

I never realized morse code was organized as a binary tree, this makes it much faster to figure out which letter the code meant

[–] Deconceptualist@lemm.ee 28 points 1 year ago* (last edited 1 year ago) (1 children)

I think if you take any set of symbols and map each one to a unique binary sequence, you can then structure it as a binary tree.

In other words Morse didn't have to be designed as a tree. The tree is just a data structure that fits any similar abstraction. You could probably do something similar with a multidimensional array (5D to include punctuation) but that's much harder to illustrate.

[–] HamsterRage@lemmy.ca 8 points 1 year ago

Yes, but it is designed that way so that the most common letters take less dits and dad's to encode. That reduces the overall work.

Well, you only got 2 symbols, so binary, and you want to minimize the symbols used for the whole alphabet+numbers. That naturally will give you a binary tree.

[–] SoonaPaana@lemmy.world 10 points 1 year ago

This is one of the best cool guides I have ever come across. Simple and efficient! Good job!

[–] Deconceptualist@lemm.ee 8 points 1 year ago* (last edited 1 year ago)

Learn in one minute, but only if you practice 10 minutes per day!

I do love the nod to Short Circuit at the end though.

I would like to add:

DAH DAH DIT DAH DAH, DIT DAH DAH DAH DAH

[–] cdf12345@lemmy.world 8 points 1 year ago (1 children)

This is also an extremely difficult way to learn Morse code. No one that actually knows Morse code will ever use a chart like this in their thinking and listening pattern.

[–] Isoprenoid@programming.dev 6 points 1 year ago (1 children)

You're right, and your post needs to be seen more. Learn Morse audibly, not visually. Whenever I see someone post about these charts it instantly tells me that they don't actually use Morse.

Learning Morse visually means you have to decode it with more steps:

hear code --> visualise the sound --> decode to letter

Decoding by ear is the fastest way, and is the way that Morse operators decode it (eventually you just hear words).

hear code --> decode to letter.

Here is a useful website for learning Morse code: https://lcwo.net/

[–] m0darn@lemmy.ca 5 points 1 year ago

There's also Morse Trainer on f-droid for those that are app inclined.

[–] KoboldCoterie@pawb.social 7 points 1 year ago

I understand why the period is a 6-sound sequence (the complexity is organized by how common the character is in use), but it bothers me that it isn't just a single "dit".

[–] ZzyzxRoad@sh.itjust.works 7 points 1 year ago

This is amazing, but if I came up with something like this and I showed somebody, they'd have me institutionalized.

[–] nieceandtows@programming.dev 6 points 1 year ago

That is pretty cool

[–] boogetyboo@aussie.zone 5 points 1 year ago

This is brilliant, thank you!

[–] RandomStickman@kbin.social 5 points 1 year ago

the most important one to learn is SOS ...---...

[–] phcorcoran@lemmy.world 1 points 1 year ago (2 children)

I guess the symbols aren't standard? The ones on the bottom table don't match with the ones in the tree

[–] snowe@programming.dev 2 points 1 year ago

I checked all of them, they all look to match to me.

[–] ChrisLicht@lemm.ee 1 points 1 year ago (1 children)
[–] Parkkid@lemmy.world 3 points 1 year ago (2 children)

So most of the symbols on the bottom are not on the chart st the top. However, the period is listed at dot dash dot dash dot dash, but the chart would make it dash dash dash dot.

[–] Rivalarrival@lemmy.today 1 points 1 year ago* (last edited 1 year ago)

DahDahDahDit has no character listed on the tree. It decodes as "Ó" (with the diacritical) in some translators.

Two other symbols (DahDahDahDah and DitDitDahDah) also have no character mapped. In some translators, they decode to "Ĥ" and "Ü", respectively, but those characters are not used in English and are not listed on this tree.

Those positions are included in the tree only because they are steps to get to Zero (DahDahDahDahDah) and Two (DitDitDahDahDah)

The tree has no punctuation listed.

[–] ChrisLicht@lemm.ee 0 points 1 year ago

..-. .- .. .-. / .–. .- .- -.. / - — / -.– — ..-