Version 2.0.0/sv - Revision history

Peder at 16:34, 27 May 2015

2015-05-27T16:34:20Z

Peder at 11:26, 22 August 2014

2014-08-22T11:26:14Z

Show changes

Peder: Undo revision 6971 by Peder Wikström (talk)

2014-08-22T11:24:31Z

Undo revision 6971 by Peder Wikström (talk)

Peder at 09:43, 21 August 2014

2014-08-21T09:43:54Z

Peder at 09:41, 21 August 2014

2014-08-21T09:41:24Z

Show changes

Peder: /* Viktigt! */

2014-04-07T13:02:34Z

Viktigt!

Peder at 12:36, 7 April 2014

2014-04-07T12:36:38Z

Peder at 11:53, 4 April 2014

2014-04-04T11:53:00Z

Peder: /* Buggfix: Fel kod för åtgärdsförslaget Fröträdsställning i hjälpdokumentationen */

2014-04-04T08:51:39Z

Buggfix: Fel kod för åtgärdsförslaget Fröträdsställning i hjälpdokumentationen

Peder: /* Sammanfattning */

2014-04-04T08:09:07Z

Sammanfattning

@@ Line 2: / Line 2: @@
 {{Languages|Version 2.0.0}}
 [[Category:Release]]
-[[newsdate::2014-04-04]]  [[language::sv| ]]
+[[Newsdate::2014-04-04]]  [[language::sv| ]]
 (Alla nyheter är inte översattta till svenska)

@@ Line 14: / Line 14: @@
 **Estimation of root rot occurrence can be calculated.
 **The county code (the so called "Dlänskod" as defined by NFI) is calculated autmatically when you import a stand register that contains coordinates. This means that [[Variable:CountyCode|CountyCode]] is not mandatory if you have entered coordinates in the stand register for each stand. If you have entered a county code, that county code will be used.
 ==RegWise and PlanWise==

@@ Line 14: / Line 14: @@
 **Estimation of root rot occurrence can be calculated.
 **The county code (the so called "Dlänskod" as defined by NFI) is calculated autmatically when you import a stand register that contains coordinates. This means that [[Variable:CountyCode|CountyCode]] is not mandatory if you have entered coordinates in the stand register for each stand. If you have entered a county code, that county code will be used.
 ==RegWise and PlanWise==

@@ Line 17: / Line 17: @@
 <startFeed />
 ====Viktigt!====
-Om du har importerat beståndsregister och använt dessa som indata, rekommenderas du att göra om simulering av trädlistor (via menyn '''Datahantering > Beståndsregister > Simulera träddata).''' Beräknade trädåldrar i ungskogar kommer då stämma bättre överens med det importerade beståndsregistret.
+Om du har importerat beståndsregister och använt dessa som indata, rekommenderas du att göra om simuleringen av trädlistor (via menyn '''Datahantering > Beståndsregister > Simulera träddata).''' Beräknade trädåldrar i ungskogar kommer då stämma bättre överens med det importerade beståndsregistret.
 <feedDate>2014-04-04</feedDate>
 <endFeed />

@@ Line 1: / Line 1: @@
 Version 2.0.0.0
 {{Languages|Version 2.0.0}}
 [[Category:Release]]
 [[newsdate::2014-04-04]]  [[language::sv| ]]
 (Alla nyheter är inte översattta till svenska)

@@ Line 36: / Line 36: @@
 Antalet inställningsmöjligheter är stort och upplevs av många nya användare som överväldigande. För att hantera detta finns det nu möjlighet att dölja avancerade inställningar. Det gör man genom att välja "Visa förenklad vy för kontrolltabeller". Den förenklade vyn visas som standard.
-I förenklad vy visas de parametrar som vi bedömmer som vanligast att man vill kunna ändra. Du kan anpassa vad som vad ska visas i den förenklade vyn. Du kan ändra fritt mellan avancerad and förenklad by, det är bara visningen som påverkas. Du kan ändra valet av vilket visningssätt som ska användas som standard via meny Inställningar > Gränssnitt. När förenklad vy används, visas bara en tabell för varje kontrollkategori, istället för flera tabeller i avnacerad vy. I förenklad vy visas dels alla parametrar som har inkluderats för visning, dels parametrar som inte är satta till systemets standard-värden. Det innebär att om du öppnar ett projekt somhar skapats i en tidigare programversion, och har ändrat någon parameter där som normalt inte ingår i förenklad vy, visas den ändå.
+I förenklad vy visas de parametrar som vi bedömmer som vanligast att man vill kunna ändra. Du kan anpassa vad som ska visas i den förenklade vyn. Du kan ändra fritt mellan avancerad and förenklad vy, det är bara visningen som påverkas. Du kan ändra valet av vilket visningssätt som ska användas som standard via meny Inställningar > Gränssnitt. När förenklad vy används, visas bara en tabell för varje kontrollkategori, istället för flera tabeller i avancerad vy. I förenklad vy visas dels alla parametrar som har inkluderats för visning, dels parametrar som inte är satta till systemets standard-värden. Det innebär att om du öppnar ett projekt som har skapats i en tidigare programversion, och har ändrat någon parameter där som normalt inte ingår i förenklad vy, visas den ändå.
 <feedDate>2014-04-04</feedDate>
 <endFeed />
@@ Line 52: / Line 52: @@
 ====Projektsidan borttagen ====
-I tiigare programversioner fanns en projektsida. Den innehöll bara information om projektets namn och databaskopplingar. Denna information har flyttats till startsidan.
+I tidigare programversioner fanns en projektsida. Den innehöll bara information om projektets namn och databaskopplingar. Denna information har flyttats till startsidan.
 <feedDate>2014-04-04</feedDate>
 <endFeed />
@@ Line 106: / Line 106: @@
 ====Ändrad förvald tillväxtfunktion====
-The default choice of using a whole stand growth model for calibrating the single-tree calculations is inactivated when creating a new project. This parameter is found in control table Production Model as "Growth Model Whole-Stand", and has been changed to "None", meaning that Björn Elfvings single-tree functions are used alone, without calibrating them with the stand-level growth model. The reason is not more accurate growth predictions per se, the differences between the models are rather small, but the single-tree growth functions used alone gives a more smooth transitions from young stand phase to the established phase, at least in a numerous cases tried.
+The default choice of using a whole stand growth model for calibrating the single-tree calculations is inactivated when creating a new project. This parameter is found in control table Production Model as "Growth Model Whole-Stand", and has been changed to "None", meaning that Björn Elfvings single-tree functions are used alone, without calibrating them with the stand-level growth model. The reason is not more accurate growth predictions per se, the differences between the models are rather small, but the single-tree growth functions used alone gives a more smooth transition from young stand phase to the established phase, at least in a numerous cases tried.
 The default function choice for calculating tree diameters for sapling trees (parameter "Sapling Diameter Model" in control table Production Model) has also been changed, from "NystromSoderberg" to "Elfving", for the same reason.
@@ Line 116: / Line 116: @@
 <startFeed />
 ==== Ny mortalitetsmodell====
-A new mortality model is available and used as default model in new project. For existing projects (created in previous program version), we recommend that you select this model instead. The model is called "Elfving" and is selected in control table Production Model. With the old model, mortality in non-dense stands have been calculated with a somewhat "primitive" model (Göte Bengtsson 1978), with a fixed mortality precentage for each species. The new model is a single-tree model based on a large set of NFI-data (Rikskogstaxeringens data). The new model also replaces the single-tree mortality model by Fridman & Ståhl which has used until now to distribute mortlaity to trees. The latter is in it basic form a stochastic model, while the new one is determinstic, and therefore better suited for Heureka. <feedDate>2014-04-04</feedDate>
+A new mortality model is available and used as default model in new project. For existing projects (created in previous program version), we recommend that you select this model instead. The model is called "Elfving" and is selected in control table Production Model. With the old model, mortality in non-dense stands have been calculated with a somewhat "primitive" model (Göte Bengtsson 1978), with a fixed mortality precentage for each species. The new model is a single-tree model based on a large set of NFI-data (Rikskogstaxeringens data). The new model also replaces the single-tree mortality model by Fridman & Ståhl which has been used until now to distribute mortality to trees. The latter is in it basic form a stochastic model, while the new one is determinstic, and therefore better suited for Heureka. <feedDate>2014-04-04</feedDate>
 <endFeed />
@@ Line 125: / Line 125: @@
 For an established stand, Heureka calculates the mean age (variable "ForestData.MeanAge excl overstorey") as the basal area weighted mean age of the trees. For a young stand, the variable is calculated as a weighted arithmetic mean age, where the calculated probabilities for crop trees (beräknade huvudstamssannolkheter) are used as weights. In established stands (mean height ≥ 7 m), tree ages are by default calibrated so that the calculated mean age and the mean age imported (for example from the stand register) are the same. This calibration has not been applied for young stands. The reason for this is that the imported mean age for young stands has not been used if a mean height has been available. In that case, the mean age has been based on the calculated sapling ages, which in turn depend on tree heights and site index. This have resulted in a more model-driven than data-driven approach, which is probably good since data for young stands are often reported as very uncertain. If relying too much on the age/height relation in young stands, there is a risk that the calculated growth for young stands with a large height/age ratio is overestimated. In stands where there have been a few years of large height growth, these few years constitute a large part of the total age of the stand and will affect growth much more in relative terms than is the case for an older stand. As a drawback, the ages for young stands calculated in Heureka have often differed from the mean ages in the stand register. Several measures has been taken to handle this, and some more will be available later this year in version 2.1.
 *One change is that by default, mean heights for young stands are ignored when simulating tree list. When simulating tree lists from stand register data, you will find a new check box "Let system automatically calculate tree heights for young stands". The corresponding function is available when entering data manually, in the sapling simulator dialog you can choose "Calculate from age" (see Figure 2a and 2b). Using this option (which is default) will result in more robust height/age-relations in young stands, and smaller differences between stand register age and age calculated by Heureka.
-*Sapling ages can now be calibrated so that the mean arithmetic age of main saplings should be close the entered mean age of the stand. The use of this calibration is activate in control table ProductionModel, parameter Calibrate Age Young Stand, which is set to True in new projects. You should change this parameter when you open old projects. Before this calibration, the program projects the growth for the number of years that differs between the mean age calculated by the model (as a function of tree heights), and the entered mean age.
+*Sapling ages can now be calibrated so that the mean arithmetic age of main saplings should be close to the entered mean age of the stand. The use of this calibration is activated in control table ProductionModel, parameter Calibrate Age Young Stand, which is set to True in new projects. You should change this parameter when you open old projects. Before this calibration, the program projects the growth for the number of years that differs between the mean age calculated by the model (as a function of tree heights), and the entered mean age.
 *Another improvement is that the start up of a young stand has been refined to better match the usage of five-year period lengths. When not using this function (by unchecking the check box), tree heights will be calibrated so that the mean height for each species is as close as possible to the entered mean height.
@@ Line 197: / Line 197: @@
 <startFeed />
 ==== Ny resultatvariabel "Stand Age" (ålder enligt beståndsregister) ====
-Heureka calculates mean age (variable "ForestData.MeanAge excl overstorey") as the basal area weighted mean age of trees in established stands. For a young stand, it is calculated as a weighted arithmetic mean age, where the calculated probabilities for crop trees (beräknade huvudstamssannolkheter) are used as weights. Typically, the calculated mean age does not increase by exactly the same value as the period length, since it is weighted. Also, the initial age may deviate from the input mean age, especially in young stands. Variable StandAge (ålder enligt beståndsregister) has been added to result category ForestData to represent age since regeneration (plus sapling age when planted which is currently hard-coded to 2 years). In period 0, it is the same as the input data, and then increases by five years per five-year period until final felling.
+Heureka calculates mean age (variable "ForestData.MeanAge excl overstorey") as the basal area weighted mean age of trees in established stands. For a young stand, it is calculated as a weighted arithmetic mean age, where the calculated probabilities for crop trees (beräknade huvudstams-sannolikheter) are used as weights. Typically, the calculated mean age does not increase by exactly the same value as the period length, since it is weighted. Also, the initial age may deviate from the input mean age, especially in young stands. Variable StandAge (ålder enligt beståndsregister) has been added to result category ForestData to represent age since regeneration (plus sapling age when planted which is currently hard-coded to 2 years). In period 0, it is the same as the input data, and then increases by five years per five-year period until final felling.
 The variable "ForestData.Stand Age" can be used in reports and in optimization problems. For example, you could replace ForestData.MeanAge with ForestData.Stand Age to keep track of the area of bare land or young forest allowed (in the optimization model).
@@ Line 264: / Line 264: @@
 <startFeed />
-==== Rättat modellfel: Fel i terrängtransportkostnader vid ystruktur eller grundförhållanden av klass 4 och 5====
+==== Rättat modellfel: Fel i terrängtransportkostnader vid ytstruktur eller grundförhållanden av klass 4 och 5====
-Beräkningen av kostnad för terrängtransport baseras på Skogforsk tidsåtgångsfunktioner. Denna är ger missvisande resultat vid svåra förhållanden. Om man anger klass 4 eller 5 för ystruktur eller lutning kan beräknad tidsåtgång t o m bli negativ. För att vara på säkra sidan används nu högst klass 3 för dessa variabler vid beräkningen av tidsåtgång.
+Beräkningen av kostnad för terrängtransport baseras på Skogforsk tidsåtgångsfunktioner. Denna är ger missvisande resultat vid svåra förhållanden. Om man anger klass 4 eller 5 för ytstruktur eller lutning kan beräknad tidsåtgång t o m bli negativ. För att vara på säkra sidan används nu högst klass 3 för dessa variabler vid beräkningen av tidsåtgång.
 <feedDate>2014-04-04</feedDate>
 <endFeed />

@@ Line 260: / Line 260: @@
 ==== Buggfix: Fel kod för åtgärdsförslaget Fröträdsställning i hjälpdokumentationen====
 This is not really a program bug, but a documentation error. The code for final felling with seed trees was defined as 16383 instead of 16384 on both the wiki and in the help documentation. This has been corrected. But the program has also been modified so that it recodes an imported treatment proposal code 16383 to 16384.
 <feedDate>2014-04-04</feedDate>
 <endFeed />

@@ Line 14: / Line 14: @@
 *Version 2 representerar ett mer välbeprövat program.
 *Användargränssnittet har förenklats och förbättrats. Dock är Heureka fortfarande ett expertsystem.
-*en del ändringar har gjorts i tillväxtmodellen. Även om du använder samma inställningar och indata som i förra versionen, kommer resultaten inte att bli exakt desamma.
+*En del ändringar har gjorts i tillväxtmodellen. Även om du använder samma inställningar och indata som i förra versionen, kommer resultaten inte att bli exakt desamma.
 *Det finns nu möjlighet att lägga in pris- och kostnadstrender.