|
|
|
Configuration preferences are read out of text files stored in the folder `config`. Gepard is shipped with two configuration templates: `default.gepard.cfg` for the programme itsself, and `default.database.json` for communication with a database server.
|
|
|
|
Gepard's configuration file, `default.gepard.cfg`, contains the default configuration of Gepard and can be left as it is. On the contrary, `default.database.json` is only a template that needs editing to enable uploading results to a database.
|
|
|
|
|
|
|
|
To change the default configuration of Gepard, copy `default.gepard.cfg` to `.default.gepard.cfg` (i.e. add a point character in the beginning) and edit it accordingly:
|
|
|
|
|
|
|
|
```
|
|
|
|
[Defaults]
|
|
|
|
# file path without "" !
|
|
|
|
file_path = .
|
|
|
|
```
|
|
|
|
|
|
|
|
When Gepard opens a file dialog (e.g. to create a new project or open an existing one) `file_path` is the location that it opens per default.
|
|
|
|
|
|
|
|
```
|
|
|
|
[Interface]
|
|
|
|
# possible values: SIMULATED_RAMAN_CONTROL, SIMULATED_FTIR_CONTROL, WITEC_CONTROL, RENISHAW_CONTROL, THERMO_FTIR
|
|
|
|
raman_interface = SIMULATED_RAMAN_CONTROL
|
|
|
|
```
|
|
|
|
|
|
|
|
This configures the connection of Gepard to a microscope. In modes `SIMULATED_RAMAN_CONTROL` and `SIMULATED_FTIR_CONTROL`, Gepard can be operated on any computer, regardless of the presence of a microscope. The other options require the corresponding devices to be present and configured to comunicate with Gepard.
|
|
|
|
|
|
|
|
If you plan on using one of the interfaces to control your device, please
|
|
|
|
note: You use this interface at your **OWN RISK**! Make sure, that no obstacles
|
|
|
|
block the objective and that you **UNDERSTAND** and **VALIDATE** the code that controls
|
|
|
|
the microscope! Start with "witectesting.py" or "renishawtesting.py" which should read and move within small margins.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|