Most commands in GeoDict can be run in the job queue. To run a command in the job queue select the desired module, e.g. FiberGeo. In the module section, select the desired functionality and edit all settings as you are used to from running simulations locally. Now, instead of running the command locally by clicking the Run / Generate button, click on the Job Queue button.

The Run Command in GeoDict Job-Queue dialog opens, where you can define multiple settings:

• Project Name: This name allows you to group multiple simulations together by giving them a shared project name. The default name originates from the name of the currently selected project folder, e.g., MyFirstGeoDictProject.
• Job Name Prefix: This name serves to identify the specific simulation that is run. The default name depends on the chosen command, e.g. FiberGeoCreate for creating fibers using FiberGeo. If multiple jobs with the same job name prefix exist within one project, the name is extended by a running number (*-001, *-002, ...).

• Upload Current Structure: When this option is activated the structure that is currently loaded in GeoDict is uploaded to the job queue server together with the job. This is necessary for modules analyzing a structure or predicting properties. The option is active by default when a structure is currently loaded in GeoDict.
• Upload Current Project folder: When this option is activated the complete current project folder is uploaded to the job queue server together with the job. This can be necessary if additional files in the project folder are required to run the computation, e.g., for continuing a FlowDict simulation from a previous result.
• Selected machine: Here you can choose the job queue server that you want to use for the simulation. The last selected server/machine used is selected by default. If only one server/machine is available, it is selected automatically. Clicking Select opens the Select server for job dialog. Here you can see all currently reachable job queue servers. For each server the Hostname, your Username on this machine, and the current number of Jobs in queue from all clients are provided. Additionally, the available hardware components and their usage can be seen: Number of logical cores, RAM in use, Total RAM, CPU utilization, and Free disk space.
  

• Timeout: This option allows you to define at timeout for the job. After the defined number of hours the job is automatically terminated. If you do not want any timeout set this value to 0. Then the simulation runs until it is finished, terminated or crashes. Setting a timeout is useful to avoid blocking the job queue server with jobs that, e.g. run into convergence problems.

After defining all settings, click on Run to send the job to the server. A dialog showing the progress of Packing, uploading and starting the job opens. For each job a python macro, based on the selected command and its settings is created and then executed on the job queue server. After the upload of the job is completed the Job Queue Projects dialog opens automatically. Here you can see the current status of the job and download the results of completed jobs.

You can execute GeoPython macros / scripts on a job queue server. For this, go to the Macro Execution Control dialog, select your macro / script and click on Run in Job Queue. Running macros in the job queue is especially useful for macros, where parameters can be varied by selecting Vary. Define multiple values for the corresponding parameters. Then, for each parameter combination of the variation a single job is created and queued on the server.

After clicking on Run in Job Queue the Run GeoPython Macro in GeoDict Job-Queue dialog opens, which is very similar to the dialog for running a single command:

• Project Name: This name allows you to group multiple simulations together by giving them a shared project name. The default name originates from the name of the currently selected project folder, e.g., MyFirstGeoDictProject.
• Job Name Prefix: This name serves to identify the specific computation that is run. The default name consists of Macro execution and the file name of the macro. This file name is extended by the parameter values. If multiple jobs with the same job name prefix exist within one project, the name is extended by a running number (*-001, *-002, ...).

• Upload Current Structure: When this option is activated the structure that is currently loaded in GeoDict is uploaded to the job queue server together with the job. This is necessary for modules analyzing a structure or predicting properties. The option is active by default when a structure is currently loaded in GeoDict.
• Upload Current Project folder: When this option is activated the complete current project folder is uploaded to the job queue server together with the job. This can be necessary if additional files in the project folder are required to run the computation, e.g., for continuing a FlowDict simulation from a previous result.
• Selected machine: Here you can choose the job queue server that you want to use for the simulation. The last selected server/machine used is selected by default. If only one server/machine is available, it is selected automatically. Clicking Select opens the Select server for job dialog. Here you can see all currently reachable job queue servers. For each server the Hostname, your Username on this machine, and the current number of Jobs in queue from all clients are provided. Additionally, the available hardware components and their usage can be seen: Number of logical cores, RAM in use, Total RAM, CPU utilization, and Free disk space.
  

• Timeout: This option allows you to define at timeout for the job. After the defined number of hours the job is automatically terminated. If you do not want any timeout set this value to 0. Then the simulation runs until it is finished, terminated or fails. Setting a timeout is useful to avoid blocking the job queue server with jobs that, e.g., run into convergence problems.
• Variable Variation: If a macro using Vary for the parameters is used, a table containing the varied parameters and all combinations of them is shown at the bottom of the dialog. Each combination is submitted as an individual job, thus 9 jobs are committed in the shown example.