Sample applications

SDK ››
Parent Previous Next

Five sample applications (Console Application projects; C#.NET v 4.5) are provided in the Software Development Kit as examples of use of the component. In all cases, focus is on the simplicity of the example provided to allow a quick start on component use.


SampleApplication_CropML performs a two-year simulation of winter wheat using the WOFOST crop model. The simulation is run under potential condition (i.e., with temperature and solar radiation as the only limiting factor to growth).


SampleApplication_CropML_SoilW links the crop models WOFOST and CropSyst (implemented in the component CropML) with the models for water infiltration, uptake and redistribution implemented in SoilW. The solution performs a two-year simulation of water-limited growth and development of wheat.


SampleApplication_CropML_SoilW_SoilT provides an example of use of one of the modelling solution currently implemented in the UNIMI.SoilT component to simulate soil temperature at different depths. It simulates two years of soil temperature at different depths as affected by variable soil water content and crop growth and development (wheat crop). The components UNIMI.SoilW and UNIMI.CropML are linked to the UNIMI.SoilT components to provide the simulation of the soil water dynamics and of root water uptake.


SampleApplication_CropML_Diseases  implements a modelling solution including the WOFOST model coupled to the InoculumPressure, DiseaseProgress and ImpactsOnPlants components. It includes a two-year simulation showing the impact of brown rust on wheat crop in terms of leaf area index reduction.


SampleApplication_CropML_Forcing provides an example of use  of the component UNIMI.Forcing linked with the crop model WARM. It simulates the impact of forcing the crop leaf area index (LAI) with LAI and NDVI values coming from external sources, and it shows the impact on LAI and aboveground biomass.


All the models are linked via adapters with a ModelRunner application (i.e., SampleApplication_Runner) that does not offer any service other than linking components. Following this logic, each component has a data-type class for interfacing with the ModelRunner, aimed at the re-use of its domain classes (e.g., CropMLDataType, SoilWDataType) and an adapter class, in which parameters value is assigned, the links with the meteorological inputs and the run of the model (e.g., AdapterWOFOST_WL, AdapterForcing).

The inputs of the modeling solution (weather and management files) can be found in the folder Runner.Solution/bin/debug/. The component CRA.Core.GDD (http://agsys.cra-cin.it/tools/gdd/help/) is linked to the applications for graphically showing the outputs of the simulations. It will open automatically when the sample application is run.The outputs are saved in the folder Runner.Solution/bin/debug/Outputs.





Created with the Personal Edition of HelpNDoc: Easily create EPub books