The first time PhytoSim is started, you will be presented with the Create an Account page of the Log in dialog box. If you don't have a PhytoSim account already use following steps to create a new account:
A new account can also be created using Account > Create account... .
Once you have created a PhytoSim account, use your email address and your PhytoSim password to log into the application. PhytoSim requires an active internet connection for authentication purposes. Only one instance of PhytoSim is allowed to run simultaneously for each account. Working offline is also possible but requires a USB copy protection dongle (sold separately by Phyto-IT). In offline mode it is not possible to install or update PhytoSim modules.
PhytoSim also allows to remember your password once you have logged in successfully. If this option is selected, PhytoSim will try to log in automatically the next time you start the application. PhytoSim will continue remembering the password until you manually log out (Account > Log out from the menu bar). All passwords are stored encrypted.
Your log in status is displayed between brackets on the module manager item of the left PhytoSim navigator.
The PhytoSim main window is divided into two parts: a navigator on the left and a display area on the right. At the top of the navigator, access to the module manager is provided. Below that, a list of installed modules is shown. Switching between modules can be achieved by clicking on the appropriate module from the module list. This causes the module area (lower part of the navigator and the right hand side of the application window) to display the module specific content.
PhytoSim by itself does not provide any functionality, this is entirely contained in modules that can be installed depending on the users' choice. As such, each user can customize the software according to his or her wishes (and budget). This allows all users to gradually increase the functionality and complexity of the software. PhytoSim can, as it were, grow with your modelling and simulation needs.
The module manager can be accessed from the navigator (first item) and is the central place to:
The upper part of the module manager shows a categorized list of all available modules. Each module has an icon, a name and also shows its version number (if installed). The module type and installation status can also be directly observed (see picture below).
The module manager toolbar provides access to several functions:

Below the module list, information on the currently selected module is given:
Clicking on one of the module action buttons in the toolbar brings up the Installation details dialog box. This dialog provides information on the modules that are going to be installed and on the installation progress. In case a paid module is selected, billing information can also be entered.
|
|
Support (PhytoSimSupport): This module provides support and updates for paid modules. One year of free support is included when purchasing a paid module. After this period you will be able to extend the support period by paying a yearly fee (499 EUR, excl. VAT). If you choose not to extend the support period, your modules will remain functional but will not be upgraded any more and you will not be able to receive support for your paid modules. After reactivating your support contract, all modules will be upgraded to their latest version. |
|
|
Offline (PhytoSimOffline): This module allows offline usage of PhytoSim using a USB copy protection dongle. The module will be activated once you have received your USB copy protection dongle and the payment is made (99 EUR, excl. VAT). Note: Only Free, Beta and Paid modules (with paid invoice) will work offline.
Note: Only one USB copy protection dongle can be purchased by each account.
Note: Broken USB copy protection dongles will be replaced free of charge once the broken dongle has been returned to Phyto-IT.
Caution: Lost USB copy protection dongles will NOT be replaced! If you want to purchase another dongle, you will need to repurchase all your paid modules.
|
PhytoSim uses workspaces to save your work. Use File > New to clear the current workspace.
When a workspace is saved (File > Save or File > Save as), the state of all the currently installed modules is stored in the workspace file. It is not possible to save the state of only a few modules.
Opening a workspace (File > Open) loads the module states contained in that file into the currently installed modules (clearing all modules first). Any workspace module state that does not have its module installed is not loaded from the file.
Although PhytoSim allows you to save files, workspaces and load data from anywhere on your computer, it is recommended to keep your files organized within the PhytoSim folder. This folder will be automatically created when PhytoSim is installed and is located in the Documents folder of your account. All references to files within the PhytoSim folder are made relative to the PhytoSim folder. This approach allows you to easily exchange workspaces with other users, irrespectively of the location of their PhytoSim folder.
Upon installation, several subfolders are created within the PhytoSim folder:
Depending on which modules are installed, other folders might appear in the PhytoSim folder. For example, the PhytoSim Modelling module creates a Library folder which will hold your model library.
PhytoSim preferences are managed from File > Preferences. The preferences window has a navigator on the left and a display area on the right. Preferences for the PhytoSim application can be managed using the PhytoSim entry at the top of the navigator. Model specific preferences can be accessed by clicking on the module name in the navigator or on the preferences icon in the module list of the PhytoSim navigator:
The user guide that you are reading right now (thanks for that by the way!) is accessible through Help > User guide or by pressing the F1 button. Pressing this button when a module is selected will take you directly to the user guide of that module. Once in the user guide window, you can switch between the different module user guides and the PhytoSim application user guide using the navigator on the left.
An online version of the latest user guide of PhytoSim and of each module is also available through the Phyto-IT website.
The support dialog (Help > Support) provides support for PhytoSim: bug reports, questions and feature requests.
You will receive a confirmation email once you have submitted a support request. Any further communication about your support request will happen through email.
| 1 | The remote server refused the connection (the server is not accepting requests). |
| 2 | The remote server closed the connection prematurely, before the entire reply was received and processed. |
| 3 | The remote host name was not found (invalid hostname). |
| 4 | The connection to the remote server timed out. |
| 5 | The operation was canceled via calls to abort() or close() before it was finished. |
| 6 | The SSL/TLS handshake failed and the encrypted channel could not be established. The sslErrors() signal should have been emitted. |
| 99 | An unknown network-related error was detected. |
| 101 | The connection to the proxy server was refused (the proxy server is not accepting requests). |
| 102 | The proxy server closed the connection prematurely, before the entire reply was received and processed. |
| 103 | The proxy host name was not found (invalid proxy hostname). |
| 104 | The connection to the proxy timed out or the proxy did not reply in time to the request sent. |
| 105 | The proxy requires authentication in order to honor the request but did not accept any credentials offered (if any). |
| 199 | An unknown proxy-related error was detected. |
| 299 | An unknown error related to the remote content was detected. |
| 201 | The access to the remote content was denied (similar to HTTP error 401). |
| 202 | The operation requested on the remote content is not permitted. |
| 203 | The remote content was not found at the server (similar to HTTP error 404). |
| 204 | The remote server requires authentication to serve the content but the credentials provided were not accepted (if any). |
| 205 | The request needed to be sent again, but this failed for example because the upload data could not be read a second time. |
| 301 | The Network Access API cannot honor the request because the protocol is not known. |
| 302 | The requested operation is invalid for this protocol. |
| 399 | A breakdown in protocol was detected (parsing error, invalid or unexpected responses, etc.). |