Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Indicating / measuring enhanced propagation conditions #308

Open
g7ruh opened this issue Sep 15, 2024 · 2 comments
Open

Indicating / measuring enhanced propagation conditions #308

g7ruh opened this issue Sep 15, 2024 · 2 comments

Comments

@g7ruh
Copy link

g7ruh commented Sep 15, 2024

Jasper,

I have mentioned this before in a slightly different way, before you added the web site graphs.

Would it be possible to add the Base Station and Aid to Navigation total

image

to the distance chart as a separate line with scale on RHS

image

My normal total Base plus AtoN is about 6-8, currently it is 12 and there is or recently has been a little more enhanced propagation as shown by the distance chart on the Station Details web page (above).

At this level (4 above average) I often see about 100 NM (as far as Calais):

image

In my post in discussions last October, there is a screen grab with 566NM distance and 29 base and AtoN stations in total (reproduced below).

305933297-91f2da74-fbfe-48af-b767-29aeafed24b3

I think there is a good correlation between Base and AtoN total and enhanced propagation at the receiving location.

Adding this to the distance graph will enable us to record to help test this and it may be useful as an alarm trigger when above a certain number.

When I mentioned this before, I suggested turning the box on top RHS of the screen a different colour using a value based on the user's Base and AtoN count, above the local 'average'. This could be automated based on a long term average (say 1, maybe 3 months) and a number above this as the alarm trigger. That way each user can set the enhanced propagation alarm to suit their location.

image

Change colour of above from white to a user selectable colour, perhaps.

The total count to act as a trigger could be added as a parameter, but may be better if it could be stored as a local average (as recorded over a month or so). To test this and use it as an alarm trigger it could just be a parameter used at run-time, likewise, initially the average could also be added as a parameter: 'new parameter' 8 13 where 8 is local average and 13 is the alarm trigger.

What do you think?
Happy to discuss further and test it if needed

Regards
Roger

@jvde-github
Copy link
Owner

Hello Roger,

it is a bit same as this discussion: #305

It is a bit of work even to add something simple to make it backward compatible with the history backup so will add something but will take a bit of time.

@g7ruh
Copy link
Author

g7ruh commented Sep 15, 2024

Hi Jasper,

Thank you. When you have something to test, let me know.

Yes that discussion points in the same direction too.

Roger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants