-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RIR flexibility and lengthened partials implementation #160
Comments
Yeah, nothing I can do for that tbh. I am planning to add a filter to the exercises where you can select the date from where u want to include them. |
I'll add a force reload for the infinite loading |
Awesome
I was thinking that might be a good idea as well and maybe adding an option to filter by mesocycles might be beneficial as well |
As for the relative overload thing i realized that i had put 0 load and 0 reps to indicate that i had skipped those exercises that day Do you think that maybe making it so that you cant put 0 as reps or load would be better for new users and possibly stop the app from breaking in the future or just leaving as it is And just a quick question while we are talking about rir is there a specific reason why you have removed negative rir Would really like to know your perspective abouts all this |
For load there is a requirement to put at least 0.25 in case of non-bodyweight exercises, in bodyweight exercises you can have any load, even negative. I forgot to restrict the reps range to minimum 1, will add that in the next patch. As for the RIR, negative RIRs would only make sense when you disable the |
i guess this was implemented in v3 i never realized that was my bad
hmm i dont seem to get why force rir matching needs to be disabled if we suppose that we did 12 reps and 3 partials we could put that as 15 reps with x load and -3 rir edit:even if we used the latter option for force rir matching i think we can use 12 as 0 rir and calculate that instead of calculating reps and load for -3rir |
RIR matching basically adjusts your reps to match the reps to allow progressive overload without leaving too many reps in the tank. Force RIR matching will decrease your reps to match the planned RIR of that microcycle (or week). If we use -3 RIR on a set, and force RIR matching is enabled, the app will reduce the reps massively (at least 3) in order to match the planned RIR in the next microcycle. If you disable it, it'll work as you want it to, the app won't reduce the reps but it will attempt to reduce the RIR which is still not ideal tbh. For LPs, I guess a completely different approach is needed. Its not something I'm prioritizing rn, I'm currently working on completely offline functionality of the app which is gonna take a while. I don't want to change the major workings of the app to avoid breaking something important. |
Ah no, exams are done. The feedback is definitely valuable and will keep this issue open for future reference, and will get back to it after the offline feature completes. |
awesome great to hear that |
Is your feature request related to a problem? Please describe.
#156
The text was updated successfully, but these errors were encountered: