Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No word count displayed #12

Open
Suyash1989 opened this issue Jul 19, 2019 · 4 comments
Open

No word count displayed #12

Suyash1989 opened this issue Jul 19, 2019 · 4 comments

Comments

@Suyash1989
Copy link

Word found per minute is the key to learn proper Morse code and it is missing completely.

@willwade
Copy link

willwade commented Mar 9, 2020

Question for you though - how would you calculate this? Would it be timing of each element.

Typically in morse "PARIS" is used. So if you send PARIS 5 times in a minute (5WPM) you have sent 250 elements (using correct spacing). 250 elements into 60 seconds per minute = 240 milliseconds per element. We are doing each letter - not whole words in morse-learn. So do you say "A": 20ms (2 units = 10ms/unit) P:" 50ms (4 units = 12.5ms/unit) etc.. and average this out? Bear in mind the really tricky bit is that morse-learn isnt teaching any inter-character timing.

https://morsecode.world/international/timing.html

It's spinning my head out how you'd work this out - any advice given and I'll see how we can implement this

@scp93ch
Copy link

scp93ch commented Mar 9, 2020

Hi, Will mentioned to me that you had this question (I run the morsecode.world site). I had a quick look at https://morse-learn.acecentre.net/ as a result.

Although you are not teaching inter-character timing, you are using it to a degree in that you have to decide when someone has stopped keying a character. The dits and dahs you are using also have a set duration. I don't know if your decoder is fussy about the pauses between parts of a character (intra-character spacing)?

I suppose what I am saying is that you inherently have a character speed / WPM in the software to at least some degree. You have a (fixed?) dit length which should determine the speed.

From what I understand, you're not trying for speed anyway.

@Suyash1989
Copy link
Author

Sorry to share this but it was such a long time ago that I have lost all the intricate ideas that came to my mind at the moment when I started the issue. I actually spent considerable amount of time with the Gboard learner. My worry about WPM was genuine and to be able to get back to the position from where I can discuss better, I shall use it all over again and arrive there. Please bear with me for a few days and I shall be back.

@willwade
Copy link

@Sep83ch - there is some speed though to this and people want to know if they are improving or not. So although End of character isn’t really a thing when using this you can press a dit and dah key quickly. The difference I think is timing is nothing like the traditional calculations because a dah is not three times a dit in two switch mode. It’s equal. I think we just measure the average letter speed - or we could measure the average dit/dah time and so some maths from that. That’s probably better

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants