There's a provision in the Aggregator for listing known bad calls so that they will not be spotted.  That depends on the node-op to do, though.  Another helpful step is to be sure that your CW segments do not include FT8 or RTTY frequencies - I know, easier said than done, particularly during contests, but we've discovered that trying to decode RTTY as CW is a major contributor to that kind of busts

73, Pete N4ZR
Check out the new Reverse Beacon Network
web server at <http://beta.reversebeacon.net>.
For spots, please use your favorite 
"retail" DX cluster.

Any tips for reducing the production of calls decoded by CW Skimmer that result in "errors" such as EE5EE, EE3E, EE5H etc? I do have CWS configured with master.dta 

Andy K3UK 

_______________________________________________
Skimmertalk mailing list
Skimmertalk@contesting.com
http://lists.contesting.com/mailman/listinfo/skimmertalk