2017-10-23, 20:33
ok, I'm relatively new and I read this thread to find out what I should actually optimize for. I'm setting up a station that shall be moved to India later. So my focus is to get all the sferics that are far away because there are no stations near by. And by the way I agree to a lot of arguments what the stations should be optimized for.
Now regarding the calculations: By default the station - once located there - might be getting good values because only detected strikes of that station will be "known" and so only those will be taken into consideration for calculation. Also there will be no other stations to compare with, so I'm asking myself what I should look for as soon as the station is there.
On the other hand I tried to compare the station with other stations around here while preparing it and it's pretty useless because they should optimize for different criteria, as meantioned above.
So what should I do? Well I faced one problem and I think that LMO (for my station https://www.lightningmaps.org/blitzortun...n_id=14922) nearly has the solution. There I have a signal view that is close to the internal one, but it also includes frequency analysis to find potential noise. Now still it's hard to distinguish between good and bad signals in detail. Will a filter setting that prevents noise lead to signals that cannot be used for detection? What is the best amplification? Do I have noise and from where?
And this is me feeling: For me the best help would be to have some information coming along with this display. So for every signal I can see there I would appreciate to get this data:
* was it used to detect a stroke?
* if yes, how far away was the stroke? Which direction?
* how many other stations were involved?
Again this is my feeling. Any ideas on that? Is it possible?
And one really off topic point. It would be helpful to optimize the mechanism to adjust the gains automatically. If the environment changes (e.g. TV or light on), then the signals get more noise. As soon as they reach the threshold I'm currently changing some settings because I think the automatic mode does not work for me very well. But then I have completely different efficiency which confuses me very much and does not help anymore at all. The approach I proposed above should still help to observe the signals. Then with this new display everyone should be able to optimize for his location in different situaltions. In the end - even when I can't influence the automatic - I can find some settings for different situations and decide offline which one to prefer and to keep as a static setting.
In India this noise challange will be much more I expect, because the invironment is a crowded city and conditions will change a lot. So the proposed analysis is one part, tuning the automatic could be an even more efficient part.
Now regarding the calculations: By default the station - once located there - might be getting good values because only detected strikes of that station will be "known" and so only those will be taken into consideration for calculation. Also there will be no other stations to compare with, so I'm asking myself what I should look for as soon as the station is there.
On the other hand I tried to compare the station with other stations around here while preparing it and it's pretty useless because they should optimize for different criteria, as meantioned above.
So what should I do? Well I faced one problem and I think that LMO (for my station https://www.lightningmaps.org/blitzortun...n_id=14922) nearly has the solution. There I have a signal view that is close to the internal one, but it also includes frequency analysis to find potential noise. Now still it's hard to distinguish between good and bad signals in detail. Will a filter setting that prevents noise lead to signals that cannot be used for detection? What is the best amplification? Do I have noise and from where?
And this is me feeling: For me the best help would be to have some information coming along with this display. So for every signal I can see there I would appreciate to get this data:
* was it used to detect a stroke?
* if yes, how far away was the stroke? Which direction?
* how many other stations were involved?
Again this is my feeling. Any ideas on that? Is it possible?
And one really off topic point. It would be helpful to optimize the mechanism to adjust the gains automatically. If the environment changes (e.g. TV or light on), then the signals get more noise. As soon as they reach the threshold I'm currently changing some settings because I think the automatic mode does not work for me very well. But then I have completely different efficiency which confuses me very much and does not help anymore at all. The approach I proposed above should still help to observe the signals. Then with this new display everyone should be able to optimize for his location in different situaltions. In the end - even when I can't influence the automatic - I can find some settings for different situations and decide offline which one to prefer and to keep as a static setting.
In India this noise challange will be much more I expect, because the invironment is a crowded city and conditions will change a lot. So the proposed analysis is one part, tuning the automatic could be an even more efficient part.
Supporting the first station in India 1974
Stations:
Stations: