Skip to content

Conversation

WhyAsh5114
Copy link
Owner

@WhyAsh5114 WhyAsh5114 commented Sep 3, 2024

Wasn't supposed to merge & indirectly close, still new to this self-PR thing

Description

A whole and complete progressive overload algorithm using the modified Bryzcki formula.

Type of change

  • New feature (non-breaking change which adds functionality)

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Copy link

vercel bot commented Sep 3, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
my-fit-jgqg ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 6, 2024 11:53am

@WhyAsh5114 WhyAsh5114 added this to the v3-stable milestone Sep 3, 2024
@WhyAsh5114 WhyAsh5114 added the v3-enhancement New feature or request for v3 label Sep 3, 2024
Added option to calculate achieved overload percentage in the Brzycki function. Algorithm works by increasing reps based on average drop-offs generated by using previous performances
@WhyAsh5114 WhyAsh5114 merged commit 21db4d8 into main Sep 6, 2024
6 checks passed
@WhyAsh5114 WhyAsh5114 deleted the 56-progressive-overload-algorithm branch September 11, 2024 03:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v3-enhancement New feature or request for v3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant