Weather routing tips - Revision history

Mclean: /* Wind forecast Age */

2014-10-15T10:16:40Z

‎Wind forecast Age

2014-10-11T06:10:56Z

‎Weather routing module parameters explained

2014-10-11T06:01:56Z

‎Wind forecast Age

2014-10-11T06:00:40Z

‎Typical routing parameters for games

2014-10-11T06:00:17Z

‎Fine tuning WR parameters

2014-10-11T05:59:57Z

‎Fine tuning WR parameters

2014-10-11T05:59:26Z

‎Typical routing parameters for games

2014-10-11T05:55:10Z

‎Typical routing parameters for games

2014-10-11T05:52:23Z

‎Weather routing module parameters explained

2014-10-11T05:51:40Z

‎Typical routing parameters for games

@@ Line 3: / Line 3: @@
 configured, the calculation can quickly scale out of control, taking a lot of memory and cpu power.
-== Wind forecast Age ==
+== Wind forecast age ==
-[[File:ConfigTime.gif|right]] One important configuration that affects both the Track designer and Weather Routing is the forecast age. This tells the program how old the current wind forecasts are. To configure that, go the the Other tab in the main program form, locate the '''Track Designer Settings''' Panel.
+An important configuration that affects both track design and weather routing is the alignment of the wind data with the start of the track. This is explained under '''Track Designer Settings''' on the [[Other Tab]].
-Select [[File:CtrlOption.gif]]'''Grid Timestamp + Time Zone''' and set your system time zone (e.g. '''3''' for GMT+3).
+<br style="clear: both" />
 == Weather routing module parameters explained ==

@@ Line 42: / Line 42: @@
 {|class="wikitable"
-|'''Example:''' With a fast PC it is practical to use a "full" polar with records from 0-180 degrees TWA at 1 degree intervals (181 records). Using a polar like this, set the number of branches to 121 to test branches 60 degrees either side of the destination. The computer will work hard doing the calculations but the results are nice!
+|'''Example:''' With a fast PC it is practical to use a "full" polar with records from 0-180 degrees TWA at 1 degree intervals. Using a polar like this, set the number of branches to 181 to test branches 90&deg; either side of the destination. The computer will work hard doing the calculations but the results are nice!
 |}

@@ Line 10: / Line 10: @@
 {|class="wikitable"
 |'''Tip:''' Click on the computer icon to import the time zone from system settings.
-|}
+|}<br style="clear: both" />
 == Weather routing module parameters explained ==

← Older revision		Revision as of 06:00, 11 October 2014
Line 107:		Line 107:

	This will test routes at 1° intervals for 90° either side of the direction to the destination. You will need a reasonably modern CPU to work with these settings. Take care if the wind requires you to sail with the destination '''aft''' of your beam.		This will test routes at 1° intervals for 90° either side of the direction to the destination. You will need a reasonably modern CPU to work with these settings. Take care if the wind requires you to sail with the destination '''aft''' of your beam.
		+	== Fine tuning WR parameters ==
		+	Tuning WR parameters if the calculation is too slow or too fast.
		+	Slow calculations are boring. Fast calculations may not reveal the best possible route.
		+
		+	If the calculation is too slow, you may:
		+	* Reduce the '''number of branches''' - Always use an odd number.
		+	* Increase '''iso point spacing''' (say from 1 to 1.5 or 2). This spaces the isochrone points.

@@ Line 86: / Line 86: @@
 If you want to know the route that will take you to a certain isochrone
 best point (for example 48h), set "Up to isochrone" parameter to 48 and recalculate.
 == Typical routing parameters for games ==

@@ Line 94: / Line 94: @@
 * Reduce the '''number of branches''' - Always use an odd number.
 * Increase '''iso point spacing''' (say from 1 to 1.5 or 2). This spaces the isochrone points.
 == Typical routing parameters for games ==

← Older revision		Revision as of 05:59, 11 October 2014
Line 115:		Line 115:
	* Check [[File:CtrlCheck.gif]]'''Use new pruning method (recommended)'''		* Check [[File:CtrlCheck.gif]]'''Use new pruning method (recommended)'''

−	This will test routes at 1° intervals for 90° either side of... You will need a ~~resonably~~ modern CPU to work with these settings.	+	This will test routes at 1° intervals for 90° either side of the direction to the destination. You will need a reasonably modern CPU to work with these settings. Take care if the wind requires you to sail with the destination '''aft''' of your beam.

← Older revision		Revision as of 05:55, 11 October 2014
Line 114:		Line 114:
	* Clear [[File:CtrlUncheck.gif]]'''Add branches at full degrees'''		* Clear [[File:CtrlUncheck.gif]]'''Add branches at full degrees'''
	* Check [[File:CtrlCheck.gif]]'''Use new pruning method (recommended)'''		* Check [[File:CtrlCheck.gif]]'''Use new pruning method (recommended)'''
		+
		+	This will test routes at 1° intervals for 90° either side of... You will need a resonably modern CPU to work with these settings.

@@ Line 80: / Line 80: @@
 |'''Tip:''' You don't have to restart the calculation if you change that, because the track tree is still in the memory. You can change it and insert the isochrones again.
 |}
 == Fine tuning WR parameters ==

← Older revision		Revision as of 05:51, 11 October 2014
Line 108:		Line 108:
	* Clear [[File:CtrlUncheck.gif]]'''Add branches at full degrees'''		* Clear [[File:CtrlUncheck.gif]]'''Add branches at full degrees'''
	* Check [[File:CtrlCheck.gif]]'''Use new pruning method (recommended)'''		* Check [[File:CtrlCheck.gif]]'''Use new pruning method (recommended)'''
−
−	~~Each isochrone set is marked with a time label (p.e. 12h, 24h)~~
−	~~This is the point '''closest''' to the WR destination.~~
−	~~Note that you cannot connect these points, because they don't belong to the same route.~~
−	~~If you want to know the route that will take you to a certain isochrone~~
−	~~best point (for example 48h), set "Up to isochrone" parameter to 48 and recalculate.~~