Difference between revisions of "Treatment Program Generator Design"
Jump to navigation
Jump to search
(Created page with '== Creating Treatment Programs for an analysis area == Klassen TreatmentProgramManager håller ihop generering av skötselprogram för ett analysområde. Algoritmen för att gö�?�') |
|||
| Line 1: | Line 1: | ||
== Creating Treatment Programs for an analysis area == | == Creating Treatment Programs for an analysis area == | ||
| − | + | The class <tt>TreatmentProgramManager</tt> manages treatment program generation for an analysis area, as follows: | |
| − | + | ||
| − | + | # <tt>ForestDomains</tt> are evaluated and each treatment unit is assigned to a domain. | |
| − | + | # For each domain: | |
| − | + | ## Treatment units are set aside for nature conservation | |
| − | + | ## For treatment units that not has been set aside, the <tt>TreatmentProgramGenerator</tt> is called and treatment programs of the desired types (unmanaged, continuous management, or even aged management, given by the user) are generated | |
| − | + | ## For treatment units that has been set aside, unmanaged treatment programs are generated by the <tt>TreatmentProgramGenerator</tt>. | |
| − | + | ||
| + | Treatment program generation requires is both performance and memory intensive. To get reasonable performance when reading from the database when treatment programs are generated, 20 treatment units are read at a time (or as many as there are left). Once treatment programs has been generated for a treatment unit, the memory allocated by that treatment unit is released (e.g. references are set to null allowing objects to be garbage collected). | ||
== Creating Continous Management and Unmanaged Treatment Programs == | == Creating Continous Management and Unmanaged Treatment Programs == | ||