What ever happened to the aero sensor that Argon was developing?? I assume it never came to market?

became the Notio.

Thx, so guess it has never become available. :(

Currently in beta

Morelock wrote:

I remember the alpha fondly ;)

Hi Chris,

I'm also very interested in helping you guys Beta test this, filled out the form.

With regards to your earlier questions of how/where to display the data post-ride, an app is great (vs GC on a desktop) so that you can get faster results in the field of what works and doesn't, allowing for faster iteration. Ideally if the main cycling computer collecting all the data can use the "lap" separation to enable the CdA calculation for the specific sections where a given item/aspect was trialed, that would probably be easiest/fastest.

The concept of an "avatar" or toolkit of sorts that can derived from numerous rides that test various aspects is very interesting, although not sure how best to be implemented. A drop-down choice of avatar component "tags" for each ride, so that as you A/B test you can assign a CdA benefit value for said tag? I don't have enough expertise in this field to say whether even if proceeding down that route the accumulated data would be correct, or if there is some amount of interference between various components that would affect their overall benefit or not.

Hi Tom- Yeah the thing is not everyone has a good half pipe course. When you don't, out and back courses with a turn around work great if you can remove the turn around. What I do right now is I hit the lap button for each direction of the out and back test, then remove the turnaround lap -- so laps 1 and 3 are the ones I want and then lap 2 has braking and the turnaround and gets removed. I wrote my own java code that reads in the fit file and then does this automatically for you because I got tired of doing it in GC/Aerolab. Actually the code does even more than that because I can have it automatically control for temperature variation and stuff like that across laps, and it can combine many runs or do them separately or whatever. Since I do a lot of testing it really helps, and I can get the answers quickly in the field if I want.

The next level for wind-tunnel aerodynamic testing may be, NO wind tunnel!

There's no good loops near you either?

Bah! Getting aero drag from field data can't possibly done accurately.

Hi,
I filled out your beta form. Since you mention real time data of various sorts as something that might be provided to the rider (and by 'real time' I assume you mean while they are riding), have you given much thought to how this would be provided? data fields on a regular bike computer, so they have to look down to see it)? Displayed in a cycling HMD (e.g., Recon Jet, EvereySight, Garmin Varia)?

Chris

If you use a "U-shaped" course, or "half-pipe" profile, you shouldn't need to brake at the turnarounds (since the uphill slows you to a crawl), so no removal necessary. Here's what that type of run ends up looking like (this is my own personal spreadsheet I put together before Aerolab was available...basically the same thing):



Of course, re-looking at your description above...I'm unclear how you're using Aerolab in the first place for the type of testing you describe, since it's intended to evaluate multiple continuous "laps"...

It always amazes me how good your VE profiles look. I bet everyone wanted you as a lab partner in Chemistry and Physics.

I'm convinced he simulates them on a computer :-)

Tom A. wrote:

The output of my VE spreadsheet typically looks smoother than Aerolab...and I sometimes wonder if it might be how the calculation for kinetic energy changes is handled. It shouldn't be a simple "delta speed over delta time" calculation on each record...a long time ago a guy named Adam Haile educated me on that point ;-) I should check with Andy F. to see how he implemented it in Aerolab.