UIComponents consists of application/components to be used either stand alone or as utility components if applications to run models.


The Weather Data Fix application allows estimating missing weather data from time series and allows generating missing data using a re-implementation of the weather generator ClimGen, to generate sintehtic time series, and to generate ClimGen parameters from the data provided. Also, CLIMA libraries are used to derive variables like reference evapotranspiration (Penman-Monteith according to the FAO paper 56), vapor pressure deficit, and daylength. The application also provides possibility for units conversions for temperature, precipitation, global solar radiation, and windspeed, providing the outputs according to the units specified below.

The AgroManagement Configuration Generator (ACG) is a Windows application to build agro-management files to be used with the AgroManagement framework (see Components, AgroManagement; the help file provided is the one of AgroManagement).

It uses the default provided dynamic link libraries for Impacts and Rules (CRA.AgroManagement.Impacts.dll and CRA.AgroManagement.Rules.dll) and other libraries specified in the file AgroManagementConfig.xml (containing classes implementing either the IRules or the IManagement interfaces) (see extending AgroManagement).

A video tutorial is available (see web resources in the help);

ACG is briefly described in the help.

Providing data views via graphical user interfaces is a common need for every application built to make use of models. If model output is generated by a modular system in which model components are interchangeable, output variables may change, thus maintaining such graphical user interfaces can be challenging and resource demanding.

A tool which can load dataset with various schema and which helps the user to visualize data in various ways would speed up application development, allowing focusing on models, rather than on user interfaces. In such a tool, whether flexibility of use is a need, providing domain specific views of data would add value both in operational use and in model development.

The component GDD (Graphic Data Display) is a Microsoft .NET component which has the specific purpose to retrieve a set of output variables and to allow displaying values either by textual tables or by several kinds of graphs. Also, reference data (e.g. data from experiments, or surveys) can superimposed to simulation results. Graphs can be saved as image files. GDD can be used as a stand-alone tool or as a component inside an application. In the former case it provides access to a file dialog to allow the user selecting a file, whereas in the latter case it can be opened inside a modeling framework directly loading the current dataset.

At this development stage, GDD accepts inputs via three different formats: XML, Microsoft Excel, and a more compact/faster binary (another component, also available, allows I/O operations with the binary format). Readers can however be extended by third parties implementing the proper interface. Each variable can be either a table column, or an entire table of the dataset, depending on the fact that it is either only time-variant or time and 1 dimension space-variant (the latter are variables that vary across soil profiles, such as soil temperature). GDD has several tab pages in which different types of data views are available.

Developing and maintaining a simulation system implies, among other things, that the parameters used can change. Composite models are made of simpler model, which can be often interchanged by alternative formulations. This means that the development and management of a simulation system may require the ability to deal with the fact that the number and type of the parameters of the composite model may change, each time a sub model is substituted. If the system is made of interchangeable components, the need of dealing with different sets of parameters is a inherent feature of the system; an alternate component may model the same domain variables, but its approaches may demand for different, model specific, parameters.

The need of changing parameters used has a primary impact on the graphical user interfaces developed for the system: such user interfaces must be easily maintenable, and they must present the same look and feel to the user. Moreover, the capability of performing a check of the correctness of parameter value should be available for each set of parameters. A parameter editor with these features must allow for changing the parameters to be edited without changing the code, hence without a need for re-compilation of the editor.

The Model Parameters Editor (MPE) is an application which allows generating a dedicated user interface for each parameter definition made available. It can group interfaces in different tabs either according to a user criterion, or according to the different model components which originate the parameters definition. The application allows either selecting parameters definitions, or it loads automatically parameters definitions from a folder of choice. A separate application is provided to build parameters definitions as an XML file. Files with parameters values can be saved/loaded from XML files (one per parameter definition); other drivers to save/load parameters can be added. A test of values adequacy (values within a range provided in their definition) is performed when saving values. Files containing parameter values can be merged (within the same definition). MPE is developed under the .NET 4.5 Framework