That said, the new native implementation is very clean and works
really well. As mark said, add the drivers, and then you're pretty
much good to go.
Jamie
> --
> _______________________________________________
> Golden-Cheetah-Users mailing list
> golden-che...@googlegroups.com
> http://groups.google.com/group/golden-cheetah-users?hl=en
>
"You don't use science to show that you're right, you use science to
become right."--xkcd
__________________
Jamie Kimberley
Postdoctoral Fellow
Department of Mechanical Engineering
The Johns Hopkins University
Office: 410.516.5162
Mobile: 217.621.8272
Fax: 410.516.4316
E-Mail:jamie.k...@jhu.edu
>
> I can say that everything else seems to be working pretty well for an
> alpha, but the one big thing that isnt working is the metrics and
> treemap. they are all gone or hidden until you start to fiddle. I'm
> sure this will get cleaned up with some default settings.
>
The chart properties are managed now. When you drag and drop a chart on
the home window and configure it the settings are saved and applied on
restart. The Analysis view doesn't use the drag/drop layout stuff yet
and so this 'bug' will disappear when it does. You just need to select a
date range for the chart to appear... I don't restore it coz it would
interfere with the layour manager, so if you have a bunch of
charts/treemaps you like then configure them on the home window for now
and remove them from the analysis view.
I am fixing up homewindow and will proly make all the views use it
soon... it just needs more work to make sure it is robust enough.
> I am going to keep trying to get the native ANT+ working, but any help
> until then would be much appreciated. again, great work on getting
> this out the door. Cant wait to experience Native ANT+
Install the latest garmin ant agent to get the latest drivers, then
disable garmin ant agent. Look for the device file in /dev or via dmesg
and you should be good to go. I run on Win7, Ubuntu, MBP 10.6 and an
iMac 10.6 with no issues.
Mark
> 1. ??_BUG_?? Garmin drivers versus ANT+ drivers and V3 : For me, the
> bottom line since the Garmin ANT agent update from Feb 4, is that realtime
> WILL NOT work if using the Garmin drivers. Using the ANT+ mac drivers
> (downloaded from ThisIsAnt) makes this work. However, I lose Garmin ANT
> agent functionality, which stinks because I only have my watch as a data
> recorder when I am outside (and the weather is improving here in the US). I
> dont know what to say, but ever since the Garmin ANT update, it's been
> maddening. If anyone has the previous rollback version of the Garmin ANT
> agent for Mac, please let me know where I can get it.
I think the bug is with ANT agent, not GC (?). Do the Garmin ANT
compatible drivers present a /dev file ?
> 2. _BUG_when starting V3, it starts up off screen and I have to pull it
> to the top. you need to actually grab the top bar area to move the app.
I have never seen this before, seems strange. Can you post a
screenshot to describe this.
> 3. _BUG_ any time there is a pop up window, you can't close the alert,
> and you must shut down the entire program.
Is this when the preferences dialog is open?
> 4. _BUG_after a ride, the analysis of the power curve returns an error
> "Maximum number of loops %d exceeded in cp modelextraction"
I suspect that is a problem in v2 too and related to the ride file.
Can you post it so we can take a look?
> 5. _BUG_many of the analysis windows look funky like the zones arent set
> up, and things are being graphed on one big ZONE 7, things like that. All
> the metrics and analyses that were displayed on V2 suffer from this
> "disconnection" from HR zones. its like the data points are floating out
> there, and the zones are crunched to one side of the other.
Have you setup your HR and Power zones in preferences? If so a
screenshot would really help, since again, this is something I have
never seen.
> 2. _BUG_some of the things on top like ATHLETES and MEASURES dont
> respond, but its alpha.
They aren't implemented yet.
> 3. in realtime, there is quite a bit of numerical data all over the
> place, and the window that plots realtime is still squeezed at the bottom.
> I dont know about you all, but I want the realtime graph much BIGGER, and
> just need power, cadence, speed, HR, time. I know this is being addressed
> in customized layouts.
I've been working on that this weekend and I think you'll be happier
when that gets committed.
> 1. possible realtime graph could put the average dashed lines to
> the right in a small gutter as opposed to cluttering up the entire realtime
> window.
Configurable UI should address this.
> 2. Would it be possible for Realtime to have a 10-20 second
> countdown before starting?
So you can clip in and get ready. Sure. It won't be implemented any
time soon tho. Calibration is higher up the list.
> 4. some of the graph labels are very hard to read, for instance the
> top of the new HrPw display. it looks cool, but I have no idea what I am
> looking at.
You can customise the font. I don't really understand this plot
either, but its an SRMwin thing that some folks understand well.
> 8. _BUG_The diary metadata should recognize "Bike" and "bike" as being
> the same thing. I added this to the list, but it still is acting like it is
> two different categories. This leads to funky looking treemaps.
Mmmm. Case-insensitive metadata... seems like a good idea, but not
sure. Wonder what other folks think?
> 9. _BUG_upload to training peaks sometimes works, sometimes doesnt. file
> rejected, then it sometimes works after a restart of the program.
This must be related to the ride file, TP.com is a bit sensitive to
gaps in recording, would be interested to see a ridefile that fails.
> 10. Tweet your ride is implemented in a contextual right click, where the
> training peaks is in the menu.
Yes. Why is this an issue?
> 1. since twitter characters are precious, how about shortening
> "Average Heart Rate" to "avgHR", with similar shorthand being used for other
> data selected. I think having the #goldencheetah tag is very good (does GC
> have a twitter feed?), but how about a bit.ly link to the website so more
> people will use/test it? This will bring big benefits of populated lobbies
> once racing is up and running. (I'm super excited about racing) -- If no one
> is maintaining a GoldenCheetah twitter feed, I'm happy to maintain it.
Noted about the shortened text. I think it should be possible to edit
the full text before it is posted.
> 11. In general, it seems like I have alot of data "benchmarks" that arent
> populating the fields. Now, I have over 20 rides moved into V3, as well as
> about 6 V3 rides, and I still dont get my CP, STS, LTS, etc.. filled into
> some of the fields.
I don't understand 'benchmarks' are these metadata fields you filled
in on V2 or are they metrics that are not getting calculated?
> I must confess that I am not sure what alot of these
> advanced exer-science metrics are, but that doesnt mean Im not willing to
> track them and learn more about what they mean for my training.
We need contextual help!
> 12. summaries and totals. if anyone ever used the garmin connect SaaS,
> they did have a pretty nice way to look at your totals for the week, etc. I
> was a heavy user of the Polar software (not thePolar SaaS), and they had
> this simple display. I like to see how many total calories I burned, and
> miles I have ridden, as well as time, maybe zones, right there on the edge
> of the calendar. We already have a calendar, why not use it to place some
> pertinent info?
You are not the first to bring this up. The ride list in the diary
view is good at grouping by different ride metrics/values, but a
tabular data view would be soooo easy to write -- you should add that
as a feature request!
> 13. Would like the ability to generate power numbers based on my trainer
> when the ride isnt performed with GC running. Basically creating a new
> Power column of data in Editor, based on my speed and the trainer formula.
Mmmm.
> Since I dont have a power unit, when I ride without GC, I will lose track
> of all power numbers and tracking. Even if my data wont be perfect because
> I'll be out on the road, having some data should be better than no data at
> all.
Mmmm.
> Thanks to Gareth for posting this OSX V3 build (sorry I couldn't build it
> myself, but I tried for an entire weekend with no luck).
Thanks for the feedback. I think the wiki could do with a detailed
'building GC on Win / Linux / Mac' its getting to be quite difficult.
Cheers,
Mark