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 635679 - skipping & gait analysis
skipping & gait analysis
Status: RESOLVED OBSOLETE
Product: chronojump
Classification: Other
Component: chronojump
0.9.x
Other All
: High enhancement
: ---
Assigned To: Xavier de Blas
Xavier de Blas
Depends on:
Blocks:
 
 
Reported: 2010-11-24 10:43 UTC by Xavier de Blas
Modified: 2021-05-25 12:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Xavier de Blas 2010-11-24 10:43:35 UTC
Try skipping at 10ms, if needed make a firmware for lower than 10 ms
Comment 1 Xavier de Blas 2010-11-25 15:24:40 UTC
Maybe the best is do skipping with only one leg, and then interpolate the other. Let's try if 10ms is needed, maybe 50ms it's ok.
Comment 2 Xavier de Blas 2011-02-16 11:52:04 UTC
do skipping with one leg, also reccomend the user to use multichronopic and do two chronopics, two legs, sinchronized. Maybe put a button of skipping 2 legs
Comment 3 Xavier de Blas 2011-03-03 17:59:05 UTC
Gait analysis can also be done with multichronopic

just write a selector in order that the user can see all what can be done with multichronopic
Comment 4 Xavier de Blas 2011-03-03 19:06:05 UTC
On MultiChronopic (from left to right (as in jumps)) put this buttons:

Skipping (both legs)
Gait analysis
Run analysis (JM Padullés)
Generic MultiChronopic

(Put also a label that says that buttons are disabled because need to connect two chronopics)

Then an extra window will appear with:
sinchronize
delete first
total distance (gait analysis and padullés)

make no think the user on synchronize and delete first, and show instructions in order to make this process.
Comment 5 André Klapper 2021-05-25 12:33:32 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/chronojump/-/issues/

Thank you for your understanding and your help.