This is a real-world question, prompted by some unusual features on my treadmill and which I thus think about while running.
In a sub-menu on my treadmill, I can select a distance that I want to run. If my unit setting is "miles", the distances offered are all multiples of 0.1 miles, but not all multiples are possible! Specifically, if I increase the distance iteratively, the first eight available options are (in units of miles): 0.1, 0.2, 0.4, 0.5, 0.6, 0.7, 0.9, 1.0. As you can see, the distances 0.3mi and 0.8mi are missing!
I decided to collect more data on which distances are possible. It seems easier to work with integer sequences, so for the purposes of this problem, I imagine working in multiples of tenths of a mile (decimile?). Then, the distances up to 100 that cannot be chosen are:
$$ 3, 8, 13, 18, 23, 28, 33, 38, 44, 49, 54, 59, 64, 69, 74, 79, 84, 90, 95, 100. $$
As you can see, the missing distances are usually 5 apart, except sometimes they are 6 apart. I checked as high as I can and this pattern continues. If I just record the missing distances that are 6 higher than the previous missing distance, I get these six before the treadmill refuses to give me distances longer than a marathon:
$$ 44,90,131,172,218,259. $$
I now have a few questions:
How are these possible distances being generated? What is the rule, pattern, or program?
Given a distance (like 49, meaning 4.9mi), how can I mathematically determine whether the distance can be selected?
Asymptotically, what proportion of distances cannot be selected?
(Note: the same restrictions on my treadmill also apply to speeds, expressed in mph, so for example 10mph cannot be selected.)