tlf-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tlf-devel] TLF in CQWW CW


From: Thomas Beierlein
Subject: Re: [Tlf-devel] TLF in CQWW CW
Date: Fri, 9 Dec 2011 16:34:51 +0100

Hi all,

thanks for the feedback and the good ideas.

Here is my plan for the next steps:

1. make bandmap configurable in logcfg.dat 
   - filtering by band, mode and dupes
   - livetime
2. skip dupes while grab ctrl-g (maybe configurable in logcfg.dat)
3. solve andys problems if possible

Following these changes I will make a release 1.1.0

Next steps after that will be fixes for cabrillo and exact frequency in
cabrillo and adif files.

The rest of the good ideas are collected and will be introduced step by
step afterwards.

I think I will be able to do most of the above until the end of year.


73, de Tom DL1JBE.

Am Thu, 08 Dec 2011 09:12:12 +0000
schrieb FS <address@hidden>:

> Hi all,
> 
> i dont have Andys Problem as well because i always filter dupes out,
> so that CTRL-G jumps to the next unworked station. Some more things
> that could be interesting regarding bandmap might be (as proposed in
> the sources):
> - have the filter conditions in the logcfg.dat (band, mode, dupes + 
> maybe max. life time of spots)
> - sort the spots around the actual working frequency (maybe in 
> intervalls to reduce load?)
> - sort for mults (at least for the contests where this info can be
> seen from the call like wwdx or wpx)
> 
> 73 Fred
> 
> 
> On 12/08/2011 06:35 AM, Thomas Beierlein wrote:
> > Hi Andy,
> >
> > I know some of your comments regarding the bandmap are still
> > unanswered. Sorry, was a busy time here. So let me try to answer
> > here and continue the discussion.
> >
> > Am Wed, 7 Dec 2011 13:24:43 +0000 schrieb
> > Andy Summers<address@hidden>:
> >> On the new bandmap, I notice that ctrl-g grabs all calls, including
> >> those you've worked.
> >
> > It grabs any call which is displayed. If you filter your display by
> > band, mode or filter out the dupes ctrl-g grabs only the next
> > *displayed* station up from your working frequency (as documented in
> > Newbandmap.txt).
> >
> >> If your S&P rate is high enough you can get into
> >> a situation where a lot of ctrl-g presses are required to get to
> >> the spot you're after. I didn't use the Cluster, BTW.
> >>
> >> On the one hand, it's useful to have worked calls in the bandmap so
> >> you know who you've just tuned through and don't wait to listen for
> >> the call. On the other hand, they get in the way of quickly
> >> grabbing spots.
> >
> > Well, it should be simple enough to not select any dupe and skip it
> > over. Let me experiment.
> >
> > One feature not documented in the original post is to selectively
> > call a special spot. Type in some characters of the call you want
> > and press Alt-g (make sure it works in your terminal) and TLF will
> > grab the first spot with that characters in the call. Be aware that
> > it will grab the first spot which matches.
> >
> >> Traversing the bandmap spots is still inconsistent for me, as I
> >> explained earlier.
> >>
> >
> >
> > I beleive you are speaking about that sentence:
> >
> >> I think I've figured out what's happening. If you tune the rig just
> >> below the frequency of a spot then hit ctrl-g it grabs that spot.
> >> Hitting ctrl-g again without retuning the rig just picks the same
> >> spot.
> >> Tune the rig HF a little and then when you hit ctrl-g it goes to
> >> the next spot. So I imagine you have some logic in there something
> >> like:
> >
> >> for (i = 0, i<  noOfSpots) {
> >>      if (currentFreq<= SpotFreq(i)) {
> >>        goto(SpotFreq(i));
> >>     }
> >> }
> >
> > No. It is a
> >
> > if (spotfreq>  currentfreq) {
> >     goto spotfrequ;
> > }
> >
> > in the case of searching upwards. It also works very stable and well
> > here.
> >
> > Maybe let us ask which rig you use? What is the frequency resolution
> > if you set a frequency and if you read the frequency back from it.
> > Normally it gets recorded down to 1 Hz resolution. The spots from
> > cluster are in 100 Hz steps and your own recorded spots (ctrl-a)
> > are as precise as your rig can report. Maybe there is some
> > discrepancy between setting frequency and aksing it back.
> >
> >
> > 73, Tom DL1JBE
> >
> >
> >
> >
> >
> 
> _______________________________________________
> Tlf-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/tlf-devel



-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--




reply via email to

[Prev in Thread] Current Thread [Next in Thread]