Hi Bill, i suposed that only <speciall calls> shud be in the <...> but i see when i checked my all.txt that normaly also the callers are marked the same... is that normal behaviour? Part of the decodes on 30m today: *134145 1 0.1 1135 ~ CR140AA <F1MWV> 73* *150530 7 0.1 1699 ~ DM152ZYA <F1MWV> 73* *152115 -10 0.2 1774 ~ OG55W <F1MWV> 73*
*081830 5 0.6 441 ~ YO/KD6SM <F6ECI> RR73* *090015 10 0.2 1822 ~ TC630MECCA <F6EQZ> 73* 085830 -16 0.4 531 ~ *<PG3N>* TC630MECCA RR73 Didnt find any match with SP5ORS calling any special long call station this afternoon. He was active CQing and mostly working EUs but none of them its <SX...> or so. 73 On Wed, Dec 12, 2018 at 9:15 PM Bill Somerville <[email protected]> wrote: > On 12/12/2018 20:06, Patrick 9A5CW wrote: > > SP5 was active 1h or more b4 i started to call the SX special call. I > > checked that in all.txt, somehow it was exctracted from earlier > decodes... > > > Hi Patrik, > > thanks for checking that, was the SP5 working a complex call QSO partner > when seen by you previously and did one of the decodes include his call > inside '<' and '>' characters? > > Clearly we are not making the best choice when hash collisions occur. > > 73 > Bill > G4WJS. > > > > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- 9A5CW - Patrik Hrvatin --... ...--
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
