After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 695585 - bug on encoder ecS paint different than powerbars
bug on encoder ecS paint different than powerbars
Status: RESOLVED FIXED
Product: chronojump
Classification: Other
Component: chronojump
0.9.x
Other All
: Normal critical
: ---
Assigned To: Xavier de Blas
Xavier de Blas
Depends on:
Blocks:
 
 
Reported: 2013-03-10 19:46 UTC by Xavier de Blas
Modified: 2015-06-16 12:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Xavier de Blas 2013-03-10 19:46:11 UTC
on ecS both curves are separated
the algorithm works the same for singleFile and !singleFile
the problem is when kinematicsF is called
is called two times, one for "e" and one for "c"
and both times the propulsive calculations... are done. Also in the e time curves e,i,c calculations are done

this can result in return values of speed, power, ... from kinematicsF referring to an ecc phase that ends in the propulsiveEnds.

this is a problem with eccentric phase but seem ok with concentric.

All this makes a different result from using paint method (separates e,i,c better) than the other methods


First thing have to be done is put an option if isometric phase want to be separated (maybe don't need and do always). Then: 
-findCurves
-the method for !singleFile
should find the curves with the method in "paint": crossMinRow

then, there will be two curves: e and c, or if isometric is considered and there's this phase: e,i,c

then call kinematicsF one time for each curve, and it will act different (don't search for propulsive in e,i. and don't need the crossMinRow method here because it will be done previoulsy)

Basically everytime there's an ecS we need a unique method to separe the curves depending on the isometric tag.