Difference between revisions of "Cascade Weight"
From TMM Wiki
Jump to navigationJump to searchm |
TMMStephenY2 (talk | contribs) |
||
| Line 6: | Line 6: | ||
}} | }} | ||
| − | + | The cascade weight field lets [[NATS]] randomly switch between two or more [[NATS4 Cascade|cascades]], giving precedence to the cascade with the higher weight. This option can be found under Biller Cascades in [[NATS4 Billers Admin|the Billers Admin]]. | |
| − | The cascade weight field lets [[NATS]] randomly switch between two or more | ||
| − | cascades. | ||
== Finding the Weight setting == | == Finding the Weight setting == | ||
| − | Go to the [[Billers Admin]] and Edit the desired cascade. | + | Go to the [[NATS4 Billers Admin|Billers Admin]] and Edit the desired cascade. |
| − | If more than one cascade | + | If more than one cascade with the same description exists in your system, then |
| − | NATS selects which cascade to use when the [[ct#Join Form|join form]] loads. This | + | NATS automatically selects which cascade to use when the [[ct#Join Form|join form]] loads. This selection is based on the total weight of all cascades that share a description. Figure 1.4 depicts how this process works: |
| − | selection is based on the total weight of all cascades that share a | ||
| − | description. Figure 1.4 depicts how this process works: | ||
[[Image:Cascade_example.jpg|frame|center||||Figure 1.4 - When NATS Selects a Cascade]] | [[Image:Cascade_example.jpg|frame|center||||Figure 1.4 - When NATS Selects a Cascade]] | ||
| − | Figure 1.4 provides an example cascade scenario that | + | Figure 1.4 provides an example of a cascade scenario that involves three |
| − | cascades all with the same description and different weight values. | + | cascades, all with the same description and different weight values. |
| − | + | ||
| − | the cascades. This "pool" contains 75 copies of the Third Cascade, 100 | + | NATS then creates a "pool" of all the similar cascades. This "pool" contains 75 copies of the Third Cascade, 100 copies of the Second Cascade, and 50 copies of the First Cascade for a total of 225. |
| − | copies of the Second Cascade, and 50 copies of the First Cascade for a | + | |
| − | total of 225. After NATS creates this pool, it randomly selects which | + | After NATS creates this pool, it randomly selects which |
cascade to use from said pool, which means that the more "entries" | cascade to use from said pool, which means that the more "entries" | ||
| − | that there are in this pool for a single cascade, the | + | that there are in this pool for a single cascade, the higher the probability it |
will be selected. | will be selected. | ||
[[Category:Also NATS4 Article]] | [[Category:Also NATS4 Article]] | ||
Revision as of 11:43, 4 June 2010
NATS 3
|
|---|
The cascade weight field lets NATS randomly switch between two or more cascades, giving precedence to the cascade with the higher weight. This option can be found under Biller Cascades in the Billers Admin.
Finding the Weight setting
Go to the Billers Admin and Edit the desired cascade.
If more than one cascade with the same description exists in your system, then NATS automatically selects which cascade to use when the join form loads. This selection is based on the total weight of all cascades that share a description. Figure 1.4 depicts how this process works:
Figure 1.4 - When NATS Selects a Cascade
Figure 1.4 provides an example of a cascade scenario that involves three cascades, all with the same description and different weight values.
NATS then creates a "pool" of all the similar cascades. This "pool" contains 75 copies of the Third Cascade, 100 copies of the Second Cascade, and 50 copies of the First Cascade for a total of 225.
After NATS creates this pool, it randomly selects which cascade to use from said pool, which means that the more "entries" that there are in this pool for a single cascade, the higher the probability it will be selected.
