Closed TClin76 closed 2 years ago
Having Low and High attributes on a SteadyState doesn't make any sense to me, but indeed it is working in this unexpected way:
Just pushed a fix for this case to the development version.
My guess is that this situation arises from visual editors transforming SteadyState intervals to Ramps and back. So if PowerLow and PowerHigh are present on a SteadyState the App will take the higher value from the 2 and use it as Power.
In this example workout all SteadyState will result in intervals of 60s at 0.70% of FTP:
<workout>
<SteadyState Duration="60" Power="0.70"/>
<SteadyState Duration="60" PowerLow="0.70" PowerHigh="0.70" />
<SteadyState Duration="60" PowerLow="0.40" PowerHigh="0.70" />
<SteadyState Duration="60" PowerLow="0.70" PowerHigh="0.40" />
<SteadyState Duration="60" Power="0.70" PowerLow="0.70" PowerHigh="0.70" />
</workout>
Here are the test cases: https://github.com/dvmarinoff/Flux/blob/85612444508da832ab021e76b465c8551ce1305c/test/workouts/zwo.test.js#L549
@TClin76 Thanks for reporting the issue!
Just pushed a fix for this case to the development version.
My guess is that this situation arises from visual editors transforming SteadyState intervals to Ramps and back. So if PowerLow and PowerHigh are present on a SteadyState the App will take the higher value from the 2 and use it as Power.
In this example workout all SteadyState will result in intervals of 60s at 0.70% of FTP:
<workout> <SteadyState Duration="60" Power="0.70"/> <SteadyState Duration="60" PowerLow="0.70" PowerHigh="0.70" /> <SteadyState Duration="60" PowerLow="0.40" PowerHigh="0.70" /> <SteadyState Duration="60" PowerLow="0.70" PowerHigh="0.40" /> <SteadyState Duration="60" Power="0.70" PowerLow="0.70" PowerHigh="0.70" /> </workout>
Here are the test cases:
I modify the zwo file and let powerHigh and powerLow have different value, and then test it in Zwift. FYI, the result will be the average of two values.
True that, just checked it in Zwift! Will update the code.
Updated the code to take the avg value if powerLow and powerHigh differ:
Merged into master, closing this one.
Hi @dvmarinoff I found that there are some zwo files downloaded from Whatsonzwift use PowerHigh and PowerLow within SteadyState Duration command. FLUX does not recognize this kind of syntax but only accept PowerHigh and PowerLow within Warmup/Cooldown Duration. In this case, FLUX shows power target =0 in this interval.