![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
Ron, John,
Thanks for the quick replies. Makes sense, and pretty much what I figured it meant. I'm familiar with the rules on finishes - and will probably use a 700'/1 mile finish for the good reasons you suggest. Although I'd prefer to use a 50' line finish...just like the good old days! I assume Winscore handles the low finish penalty automatically? Again, I didn't find it described in the Winscore manual. Or how to handle starts out the top of the cylinder. Well, it'll be a learning experience being on this side of the scoring desk for a change... Thanks, Kirk 66 |
#2
|
|||
|
|||
![]()
On Tuesday, 19 June 2012 08:47:11 UTC-6, kirk.stant wrote:
Ron, John, Thanks for the quick replies. Makes sense, and pretty much what I figured it meant. I'm familiar with the rules on finishes - and will probably use a 700'/1 mile finish for the good reasons you suggest. Although I'd prefer to use a 50' line finish...just like the good old days! I assume Winscore handles the low finish penalty automatically? Again, I didn't find it described in the Winscore manual. Or how to handle starts out the top of the cylinder. Well, it'll be a learning experience being on this side of the scoring desk for a change... Thanks, Kirk 66 Kirk, the two scenarios you mention can be the most labor intensive with WINSCORE. WINSCORE provides you with the data and you must review the options and determine what is best for the pilot. The finish penalty - Under FLIGHT LOGS you will see if any warnings have been generated. Review the warning and if one is a finish penalty WS will tell you and recommend a specific penalty value. If you choose to use that value you select 'Adjust Scores and Apply Penalties' Option, the hammer icon on tool bar, select Task Point Penalty, type in the value and make the reason code FP. Starts out the top - WS does a decent job here but it requires a review to make sure it has chosen the best start. If the person exits out the top and then goes on course all is good. However if the pilot exited the start cylinder, came back in and went out the top (more than once) the start time should be reviewed. This is accomplished by select the flight log for the pilot and right click and choose EDIT. Choose the 'Select Alternate Start Time' button and WS will show you the different options available and what the effect on the score will be. The 3rd area where WS needs help is with MAT's. WS does a good job determining what TP's were accomplished but may not get the best speed. Each flight will need to be reviewed based on what the pilot submits. All in all WS does a great job. Ron |
#3
|
|||
|
|||
![]()
On Jun 19, 10:50*am, Ron Gleason wrote:
Starts out the top - WS does a decent job here but it requires a review to make sure it has chosen the best start. Don't agree with that. WS does not provide the best solution for a SOT that re-enters the cylinder. WS can never give the best solution in this case because penalties are not applied automatically. The start solution that is provided is the one that gives best points before the penalty is applied. In my opinion WS should always apply the computed penalty but provide an alert to the scorer that a penalty has been applied. Andy |
#4
|
|||
|
|||
![]()
On Jun 19, 10:50*am, Ron Gleason wrote:
The 3rd area where WS needs help is with MAT's. *WS does a good job determining what TP's were accomplished but may not get the best speed. *Each flight will need to be reviewed based on what the pilot submits. One quick follow-up to this: Winscore *is* a good tool overall; but I have also seen it guess MATs wrong when it auto-claims a TP a second time, without the pilot visiting two other TPs before returning to the earlier TP. For example, "9, 26, 40, 26, 18" - which is not valid since the pilot returned to TP 26 too soon. The correct MAT claim would be "9, 26, 40, 18". Or perhaps "9, 26, 40, XX, 26 ,18" where "XX" is some TP that Winscore missed - or, more likely, a TP where the pilot barely nicked the 1sm cylinder and didn't get a valid GPS fix in before leaving the cylinder. Also, the recent rules-change for low finishes may not be fully incorporated into Winscore... I ran into a situation last week where Winscore applied a "rolling finish" to my task/score because I came home about 400 feet below the gate (rain at 4 miles out washed me down)... But the new finish rules stipulated I should be marked as a landout, no rolling finish allowed. It took a bit of fiddling with Winscore to get it right (partly because 9 of 12 pilots in our class didn't make it home due to the weather, so the day was devalued and I had the longest distance with my pseudo-finish so the calcs got wonky). But for the vast majority of circumstances, Winscore gets it right. --Noel |
#5
|
|||
|
|||
![]()
On Tuesday, 19 June 2012 12:53:33 UTC-6, noel.wade wrote:
On Jun 19, 10:50*am, Ron Gleason wrote: The 3rd area where WS needs help is with MAT's. *WS does a good job determining what TP's were accomplished but may not get the best speed. *Each flight will need to be reviewed based on what the pilot submits. One quick follow-up to this: Winscore *is* a good tool overall; but I have also seen it guess MATs wrong when it auto-claims a TP a second time, without the pilot visiting two other TPs before returning to the earlier TP. For example, "9, 26, 40, 26, 18" - which is not valid since the pilot returned to TP 26 too soon. The correct MAT claim would be "9, 26, 40, 18". Or perhaps "9, 26, 40, XX, 26 ,18" where "XX" is some TP that Winscore missed - or, more likely, a TP where the pilot barely nicked the 1sm cylinder and didn't get a valid GPS fix in before leaving the cylinder. Also, the recent rules-change for low finishes may not be fully incorporated into Winscore... I ran into a situation last week where Winscore applied a "rolling finish" to my task/score because I came home about 400 feet below the gate (rain at 4 miles out washed me down)... But the new finish rules stipulated I should be marked as a landout, no rolling finish allowed. It took a bit of fiddling with Winscore to get it right (partly because 9 of 12 pilots in our class didn't make it home due to the weather, so the day was devalued and I had the longest distance with my pseudo-finish so the calcs got wonky). But for the vast majority of circumstances, Winscore gets it right. --Noel What Noel says - WS get the vast majority of situations correct. What we are talking about here are the exceptions. WS has all the data and tools within it to assist the scorer and CD in determining the best way to handle these situation(s). |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
2011 WINSCORE | Ron Gleason | Soaring | 9 | April 21st 11 03:11 AM |
WinScore help | Spam | Soaring | 2 | September 6th 09 04:00 PM |
How to add an IGC validation DLL to Winscore ? | Dave Nadler | Soaring | 1 | June 18th 09 07:22 PM |
How does Winscore calculate finish altitude? | kirk.stant | Soaring | 46 | July 31st 07 07:38 PM |
Visulalizing the Finish Cylinder | [email protected] | Soaring | 44 | March 25th 05 02:10 PM |