Since GeoDict 2021, the recording of macros in GMC format is no longer supported in GeoDict. Macro files are stored in the newer GeoPy (*.py) format, that was introduced in GeoDict 2015. The GeoPy format provides more powerful capabilities since it allows using the full power of python to control GeoDict. GeoPy files cannot be edited with GeoLab, but it is possible to run GeoPy macros from GeoLab and to change the variables defined in the python macros.

GMC macros of GeoDict versions before GeoDict 2021 can be converted to a Python macro in GeoDict using the Convert GMC to Python Macro functionality.

Nevertheless, the older *.gmc format is still supported in GeoLab. GeoLab can load and edit GMC files, and all parameters in the macro file can be changed in MATLAB with the GeoLab GMC class. The information of the GeoDict commands contained in the macro file can be accessed and modified. Furthermore, new GMC files can be created from available templates and the macros can be automatically executed with GeoDict.

For a description and examples of the functions available, check the GeoLab documentation in MATLAB. The process of connecting with GeoDict and executing the macros automatically is explained there as well.

GeoPy files cannot be edited in GeoLab. However, it is possible to execute such Python macros in GeoDict from GeoLab. Furthermore, the variables which are defined in the macro can be set from GeoLab. Likewise, it is possible to automate the run of such macros with GeoLab as well. Variables can be changed every time the macro is called, and the result files can be further analyzed with GeoLab.

For the definition of variables in a GeoPy file, see the Automation chapter.

To run the macro from GeoLab, one of the options is to use geodict.m. When running it without any argument, information such as the GeoDict executable file path, version, etc. is shown.

When running it with geodict(filename), a python file can be used. The GeoDict command line options can also be considered by using geodict(filename, options). Possible options are those that can be used when running GeoDict in command line mode. For example, if the GeoDict GUI is desired, ‘--stayopen’ should be used for the options. Then GeoDict stays open after the python file is executed.

The other possibilities to run the macro from GeoLab are to use the function runMacro.m or runGeoPythonMacro.m. At least the filename of the GeoDict macro is necessary as input of the two functions. It is also possible to give a list of variable names and their desired values. With these two functions, only the variable inputs for macro files can be set, but not the general GeoDict command line options.

For example, to change the result file name, when a macro file is called from GeoLab, two steps are necessary:

1. Define the result file name as variable in the GeoPy macro:
   
   Set the variable in the function call for the ‘ResultFileName’:

2. Now, define this filename, when calling the macro from GeoLab. This can be done in two different ways:
   
   or
   

As an example, here a short GeoDict macro is recorded while generating a fiber structure with FiberGeo:

1. Start GeoDict.
2. Select Macro → Start Macro Recording… in the menu bar.
3. Keep the default file name (GeoDictMacro.py) and click OK.
   
4. Choose Model → FiberGeo, select Create Fibers from the pull-down menu in the FiberGeo section of the GUI and click Generate & Record to generate a fiber structure with the default settings.
5. Select Macro → End Macro Recording in the menu bar. The GeoDictMacro.py file is now found in the project folder.

See the Automation chapter for more information on recording macros in GeoDict.