Hello,
It looks like cluster spots older then 1 hour are removed from the cluster window.
Is it possible to extend that "time frame" to another value or may be to a specified number?
Thanks,
Evert PA2KW
cluster time frame
Re: cluster time frame
Hi,
I think it would help. I am telling it because I used in past in my old logbook and were very interesting. Please imagine this situation. We are on the station but we need to get out for a while, when we came, sometimes we need to know if a given call has been active during the time we were out.
Define how long to keep the spots and also the possibility to keep the spots from alerts would be very useful in my opinion.(Options I lost from the old logbook I used)
I think it would help. I am telling it because I used in past in my old logbook and were very interesting. Please imagine this situation. We are on the station but we need to get out for a while, when we came, sometimes we need to know if a given call has been active during the time we were out.
Define how long to keep the spots and also the possibility to keep the spots from alerts would be very useful in my opinion.(Options I lost from the old logbook I used)
73 Manuel Fernando CT1BXX
-
IW3HMH
- Site Admin
- Posts: 2988
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: cluster time frame
You know i'm usually available to listen user requests, more effectively if those requests are a single parameter in the code (that will hit a bit the performances, if increased too much, but it's not the case)...
but what could be a sufficient time frame? 2 hours? one day? what is the reason to have spots older than 1 hour in your list?
Ah, please note: 1 hour since LAST SPOT on the callsign for the same band and mode...
but what could be a sufficient time frame? 2 hours? one day? what is the reason to have spots older than 1 hour in your list?
Ah, please note: 1 hour since LAST SPOT on the callsign for the same band and mode...
Daniele Pistollato - IW3HMH
Re: cluster time frame
Daniele,
We all know that when we are waiting for the beginning of a dx expedition sometimes it begins but some minutes later they go off, to arrange some more things, meanwhile someone sent a spot. It is only to know if a given activity had been announced before to have an idea what's going on.
The same is used to keep the spots from alerts, to know the activity,
Now, to know this information, I need to go to "dxsummit" webpage and "search" for a call. The idea is to have this feature without the necessity to leave Log4Om. I hope I can give a better idea now.
A time frame of 3 or 4 hours would be very good, but associated to a filter for a given call (exact call) makes what we are looking for.
Is it important? Perhaps not, but very useful, don't you think so?
We all know that when we are waiting for the beginning of a dx expedition sometimes it begins but some minutes later they go off, to arrange some more things, meanwhile someone sent a spot. It is only to know if a given activity had been announced before to have an idea what's going on.
The same is used to keep the spots from alerts, to know the activity,
Now, to know this information, I need to go to "dxsummit" webpage and "search" for a call. The idea is to have this feature without the necessity to leave Log4Om. I hope I can give a better idea now.
A time frame of 3 or 4 hours would be very good, but associated to a filter for a given call (exact call) makes what we are looking for.
Is it important? Perhaps not, but very useful, don't you think so?
73 Manuel Fernando CT1BXX
-
G4POP
- Log4OM Alpha Team
- Posts: 11592
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: cluster time frame
Manuel
We already have thisNow, to know this information, I need to go to "dxsummit" webpage and "search" for a call. The idea is to have this feature without the necessity to leave Log4Om. I hope I can give a better idea now.
- Capture.JPG (73.48 KiB) Viewed 5155 times
73 Terry G4POP
-
IW3HMH
- Site Admin
- Posts: 2988
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: cluster time frame
I understand Manuel,
but to obtain what you need (a notification about a recent spot retained more than 1 hour) needs you keep Log4OM active and running.
And if you can keep Log4OM active and running, why not setting a cluster alert, that will send you emails or push messages to your phone even when you're away?
You can then easily recover those informations...
Believe me, it's easy to change this parameter, but reasons are a bit out of target... it's like changing your car because your actual one run out of fuel...
but to obtain what you need (a notification about a recent spot retained more than 1 hour) needs you keep Log4OM active and running.
And if you can keep Log4OM active and running, why not setting a cluster alert, that will send you emails or push messages to your phone even when you're away?
You can then easily recover those informations...
Believe me, it's easy to change this parameter, but reasons are a bit out of target... it's like changing your car because your actual one run out of fuel...
Daniele Pistollato - IW3HMH
Re: cluster time frame
Hello Daniele,
Sorry for the late reaction from my side (was to busy with qrl).
As I started this topic I will answer the initial question of Daniele.
My Logbook/cluster is running 24h a day. Why? When I come home from a days work, I would like to review the day by the filtered clusterspots and see if some activity (not necessarily a dx-pedition but also some other "random" station that is interesting for me from which I do not know a callsign in advance).
Let's make an example (which worked for me allready many times).
(1) When reviewing the day I have seen that 3B9XX has been acticve for the last 3 days for a short while on 12m around 10:00 GMT. I might decide the fourth day to stay at home and take my chance of 3B9XX to be active again around 10:00 gmt.
(2) At 01:30 OA4XX was active on 160m the last couple of days fo a while. When wakening up, I like to review the cluster list and will notice this pattern of activity. I might decide on this activity pattern to stay up for one evening and get this fellow in the logbook.
In both cases I'm not aware of this activity, and most probably won't have a specific call to start questioning the cluster.
Do I want e-mails or sms messages of all filtered clusterspots during the night or a work day? No, please no.
I think that spots (within the filter) kept up to 12 hours would do very fine.
Making this a parameter is even better and not that hard i guess.
73's, Evert PA2KW
Sorry for the late reaction from my side (was to busy with qrl).
As I started this topic I will answer the initial question of Daniele.
My Logbook/cluster is running 24h a day. Why? When I come home from a days work, I would like to review the day by the filtered clusterspots and see if some activity (not necessarily a dx-pedition but also some other "random" station that is interesting for me from which I do not know a callsign in advance).
Let's make an example (which worked for me allready many times).
(1) When reviewing the day I have seen that 3B9XX has been acticve for the last 3 days for a short while on 12m around 10:00 GMT. I might decide the fourth day to stay at home and take my chance of 3B9XX to be active again around 10:00 gmt.
(2) At 01:30 OA4XX was active on 160m the last couple of days fo a while. When wakening up, I like to review the cluster list and will notice this pattern of activity. I might decide on this activity pattern to stay up for one evening and get this fellow in the logbook.
In both cases I'm not aware of this activity, and most probably won't have a specific call to start questioning the cluster.
Do I want e-mails or sms messages of all filtered clusterspots during the night or a work day? No, please no.
I think that spots (within the filter) kept up to 12 hours would do very fine.
Making this a parameter is even better and not that hard i guess.
73's, Evert PA2KW
