I was just going to link you to Astrogenic, however I'm sure there are many users in this forum that don't have an account, but really should because there's a lot of very good information there. I compiled this from my trials and tribulations.
http://forum.astrogenic.com/Crack open a cold one. There's no easy way around it if you want accurate strikes plotted.
I know this may seem like a lot, but after you play with the parameters and see what they do, you'll be very afluent in their use.
Most importantly, make certain the maps being used are accurately cropped to ensure the most accurate ranging results. AND make sure you actually need to adjust ranging parameters! It will take at least several active days to establish if ranging is off or not and which sectors are affected, or not.
First, I used magnetic North to position my antenna. I used a magnetic deviation chart,
http://www.solarpathfinder.com/magnetic.html to determine the offset to add or subtract from the compass heading, then updated the azimuth under “Hardware” “Antenna Alignment” properties in Nexstorm.
This chart tells me to use –3 deviation (Huntsville, AL). My antenna is mounted about +1deg to mag North. The deviation I have entered for alignment is –3deg (should be -2, but -3 works better). Storms plot at a pretty exact azimuth.
Secondly, I used the following ranging parameters in this order when making software adjustments:
1. Segmented Ranging (started with a setting of 1st ring at +10, each subsequent ring I added +3 to the previous rings value for valley and generally flat topography, and kept the value at the previous rings value for hills/mountains in excess of 1000ft) This is further explained below.
2. General Strike Ranging (GSR) for TRAC (started with a setting of +5)
3. Plot Scale (started with a setting of +1.2)
4. Nighttime Upshift (Nexstorm default)
I used the above defaults for items 1-4 as a starting point. Most parameters start with adjustments to the + since I noticed that after sufficient strikes are plotted, the range decreases. For me, this seemed to be an easier way to adjust. I guess this comes from my B-52 Gunner days, as we always adjusted our Fire Control RADAR noise/gain to the positive, then backed it down if needed.
After making the above adjustments, this is how I adjust the different software parameters:
1. Segmented Ranging: NOTE: Using a topographic map helps immensely when determining a starting point for Segmented Ranging. Since I have rolling hills within 15 miles, some of which are >1000ft, I set the first ring at +10. The 2nd and subsequent rings get a bit tricky. About 40 miles to my SW, a valley starts, so I use +13 for the second ring to my SW and +16 for the 3rd, etc, etc. To my N and E, it’s the Smoky Mountains, so I use the value of my previous ring, which just so happens to be +10, for my 2nd and subsequent rings.
Then I adjust +/- values to where the strikes are plotting after a TRAC forms. A good rule of thumb I use is to wait about 20 min after the TRAC forms. The reason being that Nexstorm is getting better at plotting the longer it tracks.
2. GSR TRAC: Remember, when you make an adjustment here, it goes across all ranges and azimuths. You may have to go back to the Segmented Ranging again. When I’m generally happy with the segmented ranging, I adjust the TRAC value to nudge the plots closer or further. Remember to allow about 20-30 minutes for the TRAC to update its position if there are a few strikes/min for that TRAC. I bounce back and forth b/w using Segmented Ranging and TRAC to make further adjustments. Mine is pretty much locked in at +4.90.
3. Plot Scale Adjust: After I feel fairly confident as to my accuracy with, I use the Plot Scale Adjustment to further refine the range. Remember, if you use this to go too far positive, the strike plots will be spaced further apart. So go back to the segmented ranging if you have an area that is off in range. Mine is set at +1.12 and I haven’t moved it in the last few weeks.
4. Nighttime Upshift: I only use this 30 min after sunset/sunrise to make plot adjustments. The key here is to only make Segmented Ranging/TRAC adjustments during the day, not when Nighttime Upshift is in effect, because the values may be messed up for daytime ops. SO, you have everything where you want it, now you know how much percentage to change upshift values at night.
If you see an area out of wack, use Segmented Ranging to correct. Also, save this ranging kernel as you go along, that way if previous settings worked better, then you can go back. When I was making these adjustments, and still am, I save the kernel using a date stamp. The Sgmented Ranging continues to be the one parameter constantly getting tweaked, until I'm happy.
