tylerscott

You and me both. Text ftw!

Sure does! The default set count unless specified is one. So you could record your work like

    Movement Name:
      10 12r
      10 10r 2s
      10 8r

Just saw my bonehead mistake. This example was done before I had actually implemented the version that allowed for numeric movement names.

In order for this to parse correctly, there needs to be an ' in front of "60m" like "'60m".

Thanks for finding this. I have updated that example on the site.

I love the simplicity of this. For you, Traindown may not offer much over what you have come up with. Here is what it would look like using the inline syntax

    @ 2020/07/15; #r:hpu; #w:3; #c:3; #d:1; push: 14; 18; 14; 14; 14; 30
    @ 2020/07/14; pull: 5; 5; 5; 5
    ...

Definitely not as human readable as yours for your use case. Thanks for sharing!

Thanks for finding this. I will investigate this and make sure it is fixed!

I hadn’t yet considered it just because the metadata solves my use case of uniform rest across all sets. For varying rest periods, I can see how metadata would be suboptimal. I’ll do some noodling on this and see if there is an elegant way to make this first class. Thanks for the feedback!

Totally get it and I agree there should be a more intuitive handling of complexes that aligns with the goal of being able to convey the “training story.”

I will do some noodling on this. If you have ideas, I’d love to dialog on them. I hadn’t implemented anything beyond the basics just because I hadn’t been doing them lately. I definitely want to support your use case as a first class language feature.

Whoops. Another bad formatting. Lemme try this

    Squat:
      # bands: 200lb
      # box: 12 inches
      # rest: 45 seconds
      * wide and medium alternating
      225 2r 10s

Doh! Bad formatting. This is what I meant

    Clean: 150 2r 5s
    + Jerk: 150 5s

You totally get it and I also LOVE ledger. I hope Traindown helps you like it has helped me. I would love to get some folks working software that lets you do exactly what you describe. I will but I am slow. I would be over the moon if someone built what you described because it would both save me the effort and I would have helped contribute in some small way.

Thanks for looking!

So I do that very thing with it! I train Westside style lately coming back to it after 15 years.

I use the metadata to capture partial ranges and accommodating resistance. For example

    Bench:
      # grip: index on smooth
      # pin height: 16 inches off bench
      # chains: 100lbs
      135 5r
      225 3r
       ...

And on and on. I have added pieces to the language over the two years I’ve been using it and I hope to write a better guide (maybe short book) on how you can capture different kinds of training.

Thanks for looking!

So glad you find value in it! I was in the same boat and that’s why I made Traindown. Thanks for taking a look!

Ran out of space in the mobile app I use for HN. Wanted to make sure and thank you for the feedback!

Definitely more of a high level logging primarily of strength based training. I built it for myself and I have run the gamut of powerlifting to strongman to Olympic weightlifting and back again. Traindown is geared toward those efforts including “meta” sports like CrossFit. Thanks for looking!

Devil is in the details, for sure! I hope one day that Traindown could support such cases. For prescriptive training, I am working on a template syntax to express what you WILL DO in addition to the currently support what you HAVE DONE. I hope to wrap that up the first quarter of this year. Thanks for looking!

Yeah, for things that are measured solely in time, Traindown isn’t a good fit.

For the question of the usefulness of portability, let’s imagine StrongLifts uses Traindown and you have the ability to access that data directly as Traindown files.

Now imagine someone has developed an analytics package that slurps your owned data and that allows you to easily spot patterns that can improve your results. You could use that immediately and find value. You would not need to export whatever mess and try to make it work assuming they even let you do that.

That’s the idea, anyhow. I feel very strongly that YOU should own YOUR DATA and applications should provide value ON TOP of your data. This provides you true freedom of choice.

Yeah, for sure the first use cases were strength oriented (I like heavy things).

I have a bit in the FAQ in the Guide that hand waves how you could model things like cardio. I personally model my intervals like an example from today

Squat: # bands: 200lb # box: 12 inches # rest: 45 seconds * wide and medium alternating 225 2r 10s

I love how you did your metadata in your example. I intend to leave the language VERY open ended and hope folks build tools for athletes that provide functionality that is spec compliant (thus portable!) but leverages nuances for the given sport. Thanks for taking a look!

That is SO RAD! I’m always around if you need to spitball some ideas on how to use Traindown. tyler at greaterscott dot com. Thanks for looking and actually considering using it.

Thanks for looking! I have a number of inspirations including various shorthand syntaxes I’ve seen in my life. I’m glad this fits in!

Thanks for the kind words!

I also have a background in Olympic weightlifting and know exactly how convoluted complexes can get.

Currently, I model those as either supersets (when it fits) or I name the complex as the movement and then use the metadata to get at a data shape that mostly fits.

Example of supersets would be something like

Clean: 150 2r 5s + Jerk: 150 5s

For a clean double, single jerk. The named complex just captures the reps and weights per submovment in the metadata.

Hey folks! I would love to get some feedback on this project if you have a spare moment.

The intent is to provide a common format for training data.

By training data, I mean data you'd commonly find in a workout app. Think "Squats at 500 for 10 reps" sorta thing.

Anyhow, thanks for looking!

I’ve had great luck using ALE lately. I don’t have much experience with coc but the ALE setup process is very straightforward.

I immediately thought of this. Thanks for the link!

I never had the words to express that feeling. Tickling the brain is exactly the experience. I also love learning a new trick in Vim even after all these years.

That was great story. Thanks for sharing!

I am also struggling to think of a situation where I would want to reach for this feature. The only examples I can muster are just minor improvements to readability, like you pointed out. I would love to see a solid example where this is a must have feature.

+1 for Effective C. Great writing and diagrams.

+1 for Ale. It has simplified my Vim life.

As a former Protovis user whose mouth hit the floor the day he discovered D3, I never cease to be amazed at the quality of work Mike does. Thanks, Mike!

Thank you for providing me the phrase to describe my favorite architecture! TIL