In my S2S log:
Ah ok, yes this page is calculated on the fly, and predates the location fields.
I have noticed a logic error in the ADIF upload, so Iām currently working on fixing that.
Basically, to handle all the different formats we support, we translate to an intermediate format. That adds a bit of complexity, but ultimately makes the process simple to add a new format. In this instance, in certain circumstances, it appears the wrong intermediate location field is being set.
Now to complete the brain surgery without killing the rest of the patientā¦
2 Likes
Good luck!
Itās the famous āold cobblers written in ALGOL or JOVIAL or suchā code that predates the end of the last ice age. 
2 Likes
Fix is building now.
2 Likes
(other bugs may exist)
1 Like
I also noticed while logging a chase that the entry showed a blank distance. This, when I logged via Sotawatch and entered my grid (CM87xh) where I was at the time.
If I went into my log and edited the location field to the grid square again, same result. If I instead entered my LAT/LON, the distance showed up.
Peter - WB6POT
1 Like
This should now be fixed.
2 Likes
..If users need to find their loctation I used this site to find my
lat/long.
Geoff vk3sq
1 Like
I think having RBN for 144 would be interesting. In my area if no other place. 
One of the local ops set something up temporarily. Two other local ops activating yesterday had one picked up and spotted on RBN. Unfortunately, only the other one had posted an alert. (They self spotted, so no big deal.)
Best regards,
Drew n7da
1 Like
Iām tried reading all the many and frequent posts and I might have missed the answer. If not, it would be nice if someone from the MT would answer Richardās question. Is there a reason or was it just an oversight?
Thereās no doubt in my mind, if I cared about my Challenge activator points [which I donāt], I have no incentive - apart from the fun of it - to work a S2S on 2m/70m CW/SSB. If activators care more about their Challenge points than the normal S2S points, I can see why they might want to log the chaser by his grid ref rather than his SOTA summit reference.
Is it too late for natural justice to prevail?
Iām trying to understand the problem. If you work a S2S, you get the distance credited in both sides of the QSO. I know this because almost all of my challenge points right now are due to S2S.
Internally, S2S are a type of chase. But the distance stuff is completely independent of that.
Are they chaser points or activator points or both within the Challenge?
If I understand the posts from at least 3 posters above, the problem is not about the effect of distance on points awarded for 2m/70cm CW/SSB S2S QSOs [although it seems there might be some technical problems with logging] but that the points are chasers points only, not activator points. I think most activators wonāt care so much about their chasers points within the challenge.
Why should I get activator challenge points for working someone at home or on a non-SOTA hill but not on a SOTA summit (i.e. a S2S)?
They are both. I have 717 points in the activator section. In the chaser section, I have 627 points.
My S2S log from the day:
227 + 104 + 126 + 80 + 81 + 9 = 627 points. Which is correct for the chaser section.
My activator log for the day:
I have all the S2S included, plus two QSOs with VK3SQ, of which only one counts. This is 88km, which is added onto the 627km, which gives 715km. The extra two points are due to the fact that the distance display in the logs truncates down and the points calculation rounds up. Itās all 64 bit floating point in the back end.
2 Likes
Very interesting, Andrew,
if you say you are being credited activator points within the challenge for S2S contacts but others e.g. @G4TGJ @M0MZB [if I understood their posts correctly] are not getting activator points, it sounds like a āsquaring the circleā issue perhaps to do with the method of recording or uploading the logs.
Did you notice I fixed a bug (or two) earlier today? If they edit their upload and resubmit it should fix the issue.
Also, as I mentioned before:
Thereās no big conspiracy to deprive people of points, so itās not anything to do with
itās just a combination of me being unable to test every one of the multitude of ways people can upload and me being a fairly shit coder when a deadline looms over my head.
2 Likes
What Andrew fails to say (modesty or just that he is a professional and expects you to know this) is that he produces a test for every fix. So that now a number of bugs have been fixed, tests exist to check they donāt come back when another bug gets fixed. Of course, there can always be bugs in regressions too.
3 Likes
If it was the intention of the MT all along to award activator points for S2Ss, itās a pity that wasnāt clarified after several activators posted on here about not getting points. There were some exchanges of posts that maintained the confusion.
In any case Andrew, Iām sure I speak for many in thanking you for all your largely-unsung hard work on the software. Good to know itās just teething problems and not a rule.
1 Like
Well, Andy, the people who could give definitive answers were quite busy working on the bugs, the rest of us should have been happy to take the first post outlining the rules as gospel until told otherwise. āYour score will be 1pt/km for each QSO with a unique callsign (per summit) activated within the year, multiplied by the number of unique summits activated.ā That to me seemed quite unambiguous, and all I could have done at the time was refer you to the rules. Considering that the work was being done half a world away and half a day out of sync, a little patience was needed.
Well, Andy, the people who could give definitive answers were quite busy working on the bugs, the rest of us should have been happy to take the first post outlining the rules as gospel until told otherwise. āYour score will be 1pt/km for each QSO with a unique callsign (per summit) activated within the year, multiplied by the number of unique summits activated.ā That to me seemed quite unambiguous, and all I could have done at the time was refer you to the rules. Considering that the work was being done half a world away and half a day out of sync, a little patience was needed.
1 Like