Climbrates in CC ??
Moderator: BOD1
Climbrates in CC ??
Hi,
for a while now i noticed, that the climbrates in the CC-graphs are less, than they were in the actual reading during flight.
(Some time ago, that wasn't the case)
Although, the average shown in cc (left / richt circles) seems to be correct.
As a reference, the data from the IGC-file shown with Soaringlab. (Example from yesterdays (18.4.)17:30 flight)
for a while now i noticed, that the climbrates in the CC-graphs are less, than they were in the actual reading during flight.
(Some time ago, that wasn't the case)
Although, the average shown in cc (left / richt circles) seems to be correct.
As a reference, the data from the IGC-file shown with Soaringlab. (Example from yesterdays (18.4.)17:30 flight)
You do not have the required permissions to view the files attached to this post.
Re: Climbrates in CC ??
PS. just read, that there was an update yesterday. Maybe that issue was already addressed ?
Re: Climbrates in CC ??
AFAIK it is the average over all thermals. Also the ones before the task start. Maybe that is where the difference is?
PH-1504, KOE
-
- Posts: 55
- Joined: Tue Apr 06, 2021 4:15 pm
Re: Climbrates in CC ??
Keep in mind that what you read in flight is over-evaluated because it doesn't take into account the time you take to find the thermal, center it, etc... while condor.club just calculates it with : AltitudeGain/TimeToGainConsideredAltitude. (it's actually a good tool to know if your centering is efficient or if you need to work on it).
You get similar results when flying IRL and comparing your Evario's average with your calculator average of the entire flight.
You get similar results when flying IRL and comparing your Evario's average with your calculator average of the entire flight.
Re: Climbrates in CC ??
I'm certain, that there has been a change. In the Past, the values shown in the graph (when moving the mouse) seemed to be brutto Values.
So they were higher than the 20s average reading in the cockpit. (wich is the netto value)
Calculating the last climb (1.st post) its about 500 m in 90 sec = 5,5 ms and not around 2,2 (avg) as indicated in the graph when moving the mouse over it)
But for shure. There are issues right know, that are far more pressing.
So they were higher than the 20s average reading in the cockpit. (wich is the netto value)
Calculating the last climb (1.st post) its about 500 m in 90 sec = 5,5 ms and not around 2,2 (avg) as indicated in the graph when moving the mouse over it)
But for shure. There are issues right know, that are far more pressing.
Re: Climbrates in CC ??
Could you give me the URL of this analysis, please?
Re: Climbrates in CC ??
Never mind, I found it.
Vario displayed here is the altitude difference between considered fix and the fix located ~20 seconds before, divided by the time difference between the 2 fixes.
Vario displayed here is the altitude difference between considered fix and the fix located ~20 seconds before, divided by the time difference between the 2 fixes.
Re: Climbrates in CC ??
Raaaaaaaaaaaaaaaaaaaaaaaah.
Found a bug, indeed.
Climb rate is divided by 2... Fixing now... Fixed.
Nice catch Crakob!
Found a bug, indeed.
Climb rate is divided by 2... Fixing now... Fixed.
Nice catch Crakob!