Time to read estimates

[Karellen]

Originally Posted by davidfor

Reading estimate Lower: program:mod($$#words, 12)
Reading estimate Higher: program:mod($$#words, 10)

...

There is no attempt to make sure the values are sensible (the 12 and 10 are just numbers that I tested with). And there is no control over the formatting of the statistics on the device. That is done by the device.

I am using a Libra 2 running v4.35.20400
I added the above code to my Kobo driver as shown in the first image.

The problem is that I get some weird estimates, like...
a 10,545 word book takes between 9 - 5 hours (2nd image) (min is more than max)
a 109,767 word book takes between 3 - 5 hours
a 237,305 word book takes between 5 - 5 hours (3rd image)
a 372,000 word book has no estimates.

These estimates are not even close, hence davidfor's disclaimer. So I would like to adjust the estimates to something more realistic for me.

I am not really sure what the 12 and 10 represent in the code above.
If I want to adjust the reading speed to between 200 and 250 words per minute, what values should I use?

Also, is it possible to add other data so it is visible in the details page? I am hoping to add "Last Read" and "Rating"

[DNSB]

Here's what I am using for the time estimates. Please note that you may have to change the 24000 and 23300 to match the estimates closer to your reading speed. The mod function returns the remainder so it's not useful here. I.e., your 372,000 word book has a remainder of 0 when divided by 12 and a remainder of 0 when divided by 10.

I set those numbers as guesstimates years back and have never bothered to change them though they do yield times that are longer than my average reading time for a book. Basically, they are a reading speed of 400 wpm multiplied by 60 for the lower number of hours and about 3% less than 400x60 for the larger number of hours.

Edit: attached image
Edit2: commented on using Mod function

[Karellen]

Originally Posted by DNSB

Here's what I am using for the time estimates. Please note that you may have to change the 24000 and 23300 to match the estimates closer to your reading speed. The mod function returns the remainder so it's not useful here. I.e., your 372,000 word book has a remainder of 0 when divided by 12 and a remainder of 0 when divided by 10.

I set those numbers as guesstimates years back and have never bothered to change them though they do yield times that are longer than my average reading time for a book. Basically, they are a reading speed of 400 wpm multiplied by 60 for the lower number of hours and about 3% less than 400x60 for the larger number of hours.

Edit: attached image
Edit2: commented on using Mod function

Fantastic!! Thank you, that works

I have used a range of 210 - 275 words per minute for now which I'll tweak over time...
program:floor($$#wordcount / 16500)
program:ceiling($$#wordcount / 12600)

Now the estimates are more reasonable.
I wonder why davidfor chose to use "mod" in his example.

Thanks again.
(sorry, I have to "spread some Reputation around before giving it to DNSB again.")

[DNSB]

As far as I remember, we discussed that at the time and it was an error. That was when I started using round and later went to floor/ceiling. See my message #451 and cyberpaul's message #472 in the original thread for more on this.

[fogice]

Originally Posted by Karellen

I have used a range of 210 - 275 words per minute for now which I'll tweak over time...
program:floor($$#wordcount / 16500)
program:ceiling($$#wordcount / 12600)

In my version, I've changed that to

program:ceiling($$#words / 2095)/10

which gives me value in hours with one decimal place. I back-calculated the '2095' value by checking about 10 books on my Kobo for the actual time it took me to read them. If you like the numbers you used above, just strike one 'zero' off the end.