Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
working_with_subregions [2026/08/31 02:12] hermann |
working_with_subregions [2026/08/31 02:26] (current) hermann |
||
|---|---|---|---|
| Line 158: | Line 158: | ||
| </code> | </code> | ||
| - | [[Patcher]] returns three outputs, and this example only stores one of them. ''corrodedProbabilities'' — the probability surface with used-up areas depleted — and ''remainingChanges'' — a Change Matrix of whatever couldn't be placed, given the current ''neighborWindowLines''/''neighborWindowColumns''/''pruneFactor'' — are both genuinely useful diagnostics in a real model, not values to ignore on principle. They're discarded here only because this page is illustrating region-manager mechanics rather than full Patcher diagnostics. All three outputs are still named explicitly, with the unwanted two bound to ''_'', following EGO Script's documented convention for discarding outputs from a multi-output nominal binding — each output is either bound to a variable or explicitly discarded with ''_'', never left out of the block. | + | [[Patcher]] returns three outputs, and this example only stores one of them. ''corrodedProbabilities'' — the probability surface with used-up areas depleted — and ''remainingChanges'' — a Change Matrix of whatever couldn't be placed, given the current ''neighborWindowLines''/''neighborWindowColumns''/''pruneFactor'' — are both genuinely useful diagnostics in a real model, not values to ignore on principle. They're discarded here only because this page is illustrating region-manager mechanics rather than full Patcher diagnostics. Binding a discarded output to ''_'' isn't required — an unwanted output can simply be left out of the block entirely — but naming ''corrodedProbabilities'' and ''remainingChanges'' explicitly here signals that they were considered and deliberately skipped, not overlooked. |
| A model that does care about ''remainingChanges'' would most likely want it accumulated across regions too, the same way [[#computing_per-class_areas_within_each_region|the area-by-region example]] accumulates its table with [[Mux Table]] — checking, once the loop finishes, whether any region failed to place all of its requested changes. | A model that does care about ''remainingChanges'' would most likely want it accumulated across regions too, the same way [[#computing_per-class_areas_within_each_region|the area-by-region example]] accumulates its table with [[Mux Table]] — checking, once the loop finishes, whether any region failed to place all of its requested changes. | ||