FlowingData Forums » your.flowingdata

athletic interval training logs

Started 7 months ago by michaeldbeavers / 5 posts

  1. I did a pyramid interval session yesterday on my bicycle trainer and want to start recording workouts that are structured like this. I'm sure there are some that come with bike computers and heart rate monitors, but I don't think I need all that gadgety.

    My requirements:
    Something with a calendar
    Infographics/charts
    comments fields
    records interval data (off time, on time, warm-up, cool-down), perhaps expressed as:
    15 WU
    5x2off/5on
    10 CD
    Total time, etc.

    How do I do this in AFD?

  2. um, do you mean YFD?

    One thing you could do is record each time separately. for example, when you're done with the workout, you could tweet:

    offtime 10
    ontime 20
    warmup 10
    cooldown 10

    where the numbers are minutes or duration. then you could put together a custom page (dropdown menu on top right corner on YFD) that shows those four metrics.

    recording all those other numbers might be kind of tricky.

  3. How about something like parsing a "splits" parameter and a note-taking feature?

    You could keep unstructured "notes" (a Django TextField) and then .split(',') anything after "splits:" before the next whitespace (or eof). So for example:

    d yfd workout Short Crown splits:27.3,43.4,67.8,69.2,71.2,68.9,43.2,27.9

    The workout "Short Crown" is specified free-form in a note somewhere and YFD doesn't need to worry about the specifics of what that entails; all that matters is how your "Short Crown" splits change over time.

  4. hmm, interesting. how do you think the "splits" could be stored?

  5. This is exactly what I'm looking for as well. @nathany - I would track them as rows in a related table: I would have a foreign key in the new table that refers to the primary key of the current measurement table. For convenience, I would also track that a measurement has splits.

    To get the data back out for display purposes, I would make a second sql query (if the measurement is marked as having splits). If you were worried about the performance of making a second query, you could join the tables in the first query. But that would make your code more complex, so I would personally choose the first.

    If you want help or want to discuss this more outside of the thread, feel free to send me an email. I mainly develop in Java, but have dabbled in almost everything, so I'd be willing to help out to make this feature happen.


Reply

You must log in to post.

About this Topic