I’ve been playing around with NHC and the SWNHC3.xls file to calculate personal handicaps using PY and the calculation method utilised on the PYS website. Since I’m working with PY I’ve set the RatingConvert setting to Off on the config sheet, so that the PY don’t get converted to TCF when loaded in to Excel to make it easier to work with familiar numbers. This works fine until it loads the revised PY ratings back into the Sailwave file, as all the ratings end up as either 0 or 1 rather than the expected 3-4 digit PY numbers. Is it expecting to have a TCF rating to load rather than a PY rating? I can obviously get around this by converting the PY to a TCF (I assume TCF=1000/PY), but I’m sure others will come across the same problem in the future.
Love the flexibility this provides and it will simplify my work load significantly when doing the calculations in the future.
I’m just off to the National Watersports Festival to do the results there. Will have a look at the code as soon as I get back but there is code in there which does an autoconvert - will have to check how it works. Yes your assumption is correct - the only issue is rounding issues.
Just to clarify you are using PY numbers in Sailwave and in the spreadsheet and the rating convert is turned off.
I’m just off to the National Watersports Festival to do the results there. Will have a look at the code as soon as I get back but there is code in there which does an autoconvert - will have to check how it works. Yes your assumption is correct - the only issue is rounding issues.
Just to clarify you are using PY numbers in Sailwave and in the spreadsheet and the rating convert is turned off.
I’ve been playing around with NHC and the SWNHC3.xls file to calculate personal handicaps using PY and the calculation method utilised on the PYS website. Since I’m working with PY I’ve set the RatingConvert setting to Off on the config sheet, so that the PY don’t get converted to TCF when loaded in to Excel to make it easier to work with familiar numbers. This works fine until it loads the revised PY ratings back into the Sailwave file, as all the ratings end up as either 0 or 1 rather than the expected 3-4 digit PY numbers. Is it expecting to have a TCF rating to load rather than a PY rating? I can obviously get around this by converting the PY to a TCF (I assume TCF=1000/PY), but I’m sure others will come across the same problem in the future.
Love the flexibility this provides and it will simplify my work load significantly when doing the calculations in the future.
Yes you understand correctly, PY numbers in both Sailwave and the spreadsheet with rating conversion turned off. I’m having to convert the final adjusted PY to a TCF to get it to load correctly back into Sailwave.
I’m just off to the National Watersports Festival to do the results there. Will have a look at the code as soon as I get back but there is code in there which does an autoconvert - will have to check how it works. Yes your assumption is correct - the only issue is rounding issues.
Just to clarify you are using PY numbers in Sailwave and in the spreadsheet and the rating convert is turned off.
I’ve been playing around with NHC and the SWNHC3.xls file to calculate personal handicaps using PY and the calculation method utilised on the PYS website. Since I’m working with PY I’ve set the RatingConvert setting to Off on the config sheet, so that the PY don’t get converted to TCF when loaded in to Excel to make it easier to work with familiar numbers. This works fine until it loads the revised PY ratings back into the Sailwave file, as all the ratings end up as either 0 or 1 rather than the expected 3-4 digit PY numbers. Is it expecting to have a TCF rating to load rather than a PY rating? I can obviously get around this by converting the PY to a TCF (I assume TCF=1000/PY), but I’m sure others will come across the same problem in the future.
Love the flexibility this provides and it will simplify my work load significantly when doing the calculations in the future.
I’m just off to the National Watersports Festival to do the results there. Will have a look at the code as soon as I get back but there is code in there which does an autoconvert - will have to check how it works. Yes your assumption is correct - the only issue is rounding issues.
Just to clarify you are using PY numbers in Sailwave and in the spreadsheet and the rating convert is turned off.
I’ve been playing around with NHC and the SWNHC3.xls file to calculate personal handicaps using PY and the calculation method utilised on the PYS website. Since I’m working with PY I’ve set the RatingConvert setting to Off on the config sheet, so that the PY don’t get converted to TCF when loaded in to Excel to make it easier to work with familiar numbers. This works fine until it loads the revised PY ratings back into the Sailwave file, as all the ratings end up as either 0 or 1 rather than the expected 3-4 digit PY numbers. Is it expecting to have a TCF rating to load rather than a PY rating? I can obviously get around this by converting the PY to a TCF (I assume TCF=1000/PY), but I’m sure others will come across the same problem in the future.
Love the flexibility this provides and it will simplify my work load significantly when doing the calculations in the future.