|
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.
|
|
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.
|
|
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:
|
|
To change the default configuration of Gepard, copy `default.gepard.cfg` to `.gepard.cfg` (please take note of the '.' at the beginning of the filename) and edit it accordingly:
|
|
|
|
|
|
```
|
|
```
|
|
[Defaults]
|
|
[Defaults]
|
... | @@ -17,7 +17,7 @@ When Gepard opens a file dialog (e.g. to create a new project or open an existin |
... | @@ -17,7 +17,7 @@ When Gepard opens a file dialog (e.g. to create a new project or open an existin |
|
raman_interface = SIMULATED_RAMAN_CONTROL
|
|
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.
|
|
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 communicate with Gepard.
|
|
|
|
|
|
If you plan on using one of the interfaces to control your device, please
|
|
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
|
|
note: You use this interface at your **OWN RISK**! Make sure, that no obstacles
|
... | @@ -25,6 +25,20 @@ block the objective and that you **UNDERSTAND** and **VALIDATE** the code that c |
... | @@ -25,6 +25,20 @@ block the objective and that you **UNDERSTAND** and **VALIDATE** the code that c |
|
the microscope! Start with "witectesting.py" or "renishawtesting.py" which should read and move within small margins.
|
|
the microscope! Start with "witectesting.py" or "renishawtesting.py" which should read and move within small margins.
|
|
|
|
|
|
|
|
|
|
|
|
To use Gepard with a Renishaw microsope, you need to provide the path to the measuring templates, as well as the size of the images recorded by your camera in the dedicated section:
|
|
|
|
```
|
|
|
|
[Renishaw]
|
|
|
|
#information specific for renishaw control
|
|
|
|
#image micrometer sizes for bright and dark field camera, format: width*height
|
|
|
|
#please insert, as it would represent an image at 1x magnification
|
|
|
|
#if unavailable, export an image from the Renishaw Camera viewer. Export as jpeg (without axes) and, within Gepard, go to Tools->ConfigureInstrumentControl.
|
|
|
|
img_size_BF = 9016.0*5748.0
|
|
|
|
img_size_DF = 4524.0*2874.0
|
|
|
|
#Path to measuring templates (*.wxm)
|
|
|
|
measTemplatePath = C:\RamanData
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
... | | ... | |