UPDATE: The filter is no longer indexing duration of run. (but will in the future).
The following are examples of valid entries, the keywords in bold what the filter is looking for.
VALID ENTRIES
- I saw a vulture while doing my 12 mile run… I think it was waiting for me to die!
- Ran 4.33 miles today. Time for dinner, season finale of #designstar and VMAs!
VALID ENTRIES w/TIME: (time will be used in the future, for now it is optional.)
- Successfully completed a 6.5 mile run in 1:07:15 with no walking breaks.
- Ran 7.71 miles in 0:50:47 @ 6:35/mile and feeling great!
INVALID ENTRIES or FAILED ENTRIES
- Just pounded out 4 miles tonight in prep for my 12 mile run. (COMMENT: Wrong run captured. Filter doesn’t know what pounded out means.)
- Finished some Taco Bell for lunch. Back to work, then the fair, then a 23 mile run tomorrow morning. (COMMENT: This simply isn’t a run, what is one to do.)
- Ran the mile today. Blah but didn’t do to bad. 11:14 not perfect but I’m not dead either (COMMENT: This could be a future feature, written out distances, it’s been added to the list.)
- 18 running miles (COMMENT: ‘running’ is not part of the filter)
- 25miles (COMMENT: no space and no mention of ‘run’. 25-mile run would also fail.)
- nothing special, but my weekend miles were 14.5 miles (COMMENT: ran 14.5 miles would have worked)
This should be looked http://twunlog.com/mekiser lot of examples that the parser should be picking up.
Thank you! We’re always looking for examples to improve the parser.