You can find all dialogs for managing the GeoDict Cloud under the Cloud & Queue entry in the menu bar.

The Login to GeoDict Cloud option is only active if you are not currently logged in. Click it to open the Login to GeoDict Cloud Service dialog, where you can enter your Username, Password, and the currently valid One-time Code from your authenticator to log in.

Clicking the Logout from GeoDict Cloud option, directly logs you out from the GeoDict Cloud. If you are not logged in, this option is inactive.

The GeoDict Cloud Projects option brings you to the corresponding dialog, where you can see all your jobs in the cloud and their associated status.

The status of a job can be:

• Simulation Starting: The cloud machine for this job is currently starting.
• Simulation Running: The simulation for this job is currently running on the cloud machine.
• Completed: The simulation for this job has been completed. The cloud machine has been shut down.
• Downloaded: The results from this job have been downloaded. You can download the results multiple times as long as the job is not deleted.
• Error: The simulation for this job has not finished and is not running anymore. This could be due to termination, the simulation failing, or running into the defined timeout.

You can sort the jobs by their Names or their Created time in the upper right corner of this dialog

To start a simulation in the cloud, enter the simulation parameters as usual in GeoDict by clicking on the Edit button in the module section. After setting up all parameters, click the Cloud button instead of the Run button.

If you are not logged in, the Login to GeoDict Cloud Service window opens. Enter your Username, Password, and your One-time code from the authenticator. Click OK to continue to the Run Command in GeoDict Cloud dialog. If you are already logged in, the Run Command in GeoDict Cloud dialog opens directly.

The Run Command in GeoDict Cloud dialog offers several settings:

• Project Name: This name allows you to group multiple simulations together by giving them a shared project name. The default name is derived 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., GrainGeoCreate for creating grains using GrainGeo.

• Upload Current Structure: When this option is activated the structure that is currently loaded in GeoDict is uploaded to the cloud machine together with the job. This is required for commands which operate on the current voxel structure, which is true for most simulation commands. Therefore, this 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 cloud machine 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. We suggest preparing a new project folder for this purpose, containing only the required data to avoid uploading unnecessary files.
• GeoDict Version: Select the GeoDict Version that you want to use. You can only select the same major version as you are running locally, e.g., GeoDict 2025. But you can choose between different service packs, if they are available on your cloud environment. Note that this allows you to e.g. test a new Service Pack release before installing it locally.
• Select Machine: Here you can select which type of cloud machine you want to use for the simulation. You can see the Number of (#) cores, the RAM, and if a GPU is available. To see cloud machines with one or more GPUs, enter a value in the Number of GPUs box. GPUs are necessary to effectively use AI functionalities in GeoDict (e.g., GeoDict-AI, FiberFind-AI). Click in the checkbox of the machine type that you want to use for this job.
  

• Timeout: This option allows you to define a timeout for the job in hours. If the job has not completed after the given time, it is automatically terminated. The maximum value is 720 h (30 days). If you do not want any timeout, set this value to 0. Then the simulation runs until it is completed, terminated or crashes. Setting a timeout can be useful to avoid additional costs, e.g., for simulations that fail to converge.

After defining all settings, click Run to send the simulation job to the cloud. You will then see a dialog showing the progress of packing the job and sending it to the cloud. All your custom GeoDict settings (e.g., your material database) are also automatically packed and sent together with the job. This ensures that the same settings are applied for local and cloud machine simulations.

Depending on your account configuration, the number of simultaneous virtual machine instances might be limited to protect you from accidental overspending. If you submit more jobs than the limit, you will receive an error message during the upload. Although those jobs will be shown as Ready in the GeoDict Cloud Projects dialog, there is currently no functionality to start these jobs. Delete these jobs and wait for other jobs to finish before resubmitting the simulation.

After the upload is completed, the GeoDict Cloud Projects dialog opens automatically. Here you can see the current status of your submitted job as well as all other jobs that you have in the GeoDict Cloud. Press Refresh (or F5) to update the view. You can close the dialog and continue to work with GeoDict locally. Open the dialog any time by selecting Cloud & Queue → GeoDict Cloud Projects in the menu bar.

When a simulation is completed, the virtual machine shuts down automatically and the status of the job changes to Completed. You can now download the results.

Click Show Log to see the current GeoDict log output for this simulation. This information can help you to observe the progress of the computation or identify potential errors. The dialog shows the last 50 lines of the log output. For running simulations, you can update the log by closing the dialog and clicking the Show Log button again.

Select one or more running simulations in the GeoDict Cloud Projects dialog and click Terminate Simulation(s) to cancel them. Only running simulations can be terminated. Before a simulation is terminated, a warning message is shown asking you to confirm that you want to terminate all listed simulations. Note that currently no partial results will be available for terminated simulations.

When the simulation is completed successfully, the status of the job changes to Completed in the GeoDict Cloud Projects dialog. Select the job (or multiple) and click on Download Results. The Select Files to Download dialog opens. Here you can only choose to download all files in the Result Data.  Note that for failed simulations (in the Error state) partial results might still be available for download, depending on the error cause.

Click OK and select a location where the result files should be stored. The files are downloaded and unpacked automatically to the selected location. A sub-folder is created for each Project Name. Within this folder, another sub-folder for each Job Name is created. Thus, the results of multiple simulations are automatically grouped into your different projects when downloading. Inside the Job Name folders, you can find the GeoDict results (*.gdr, result folder), the input python scripts to run the command (macro.py, runme.py), and the log file of the cloud machine (geodict.log). A message will inform you that the download and unpacking has successfully finished, and where you can find the data.

Click the Delete Job(s) button to delete the currently selected job(s) and all associated results. This will remove all generated files for these jobs from the Cloud Data section. Before a job is deleted, a warning message is shown asking you to confirm that you want to delete the selected jobs. After deleting, the results will not be available anymore. Thus, ensure that you have downloaded all results beforehand. Note that running jobs can not be deleted - they have to be terminated first.

You can also view all your simulations submitted from GeoDict to the cloud in the cloud web interface. Follow the same link that you received for your first login and log in using your credentials. In the Cloud Dashboard you can see information on the currently Running Cloud Machines, all available Jobs, and the stored Cloud Data. The cloud web interface is the same as the Math2Market Cloud.

In the Running Cloud Machines panel, you can see all currently running cloud machines. The User is always your username for the GeoDict Cloud. In contrast to machines started manually from the web dashboard, machines started for GeoDict Cloud simulations are automatically terminated once the simulation is finished, has failed or the timeout has expired. Click here for more details on the Running Cloud Machines panel.

In the Jobs panel, you can see all jobs submitted to the GeoDict Cloud. They can be identified by their Project and Job Name. You can see the timestamps for creation and termination. The Finished date is only available when a simulation is completed, failed or the timeout has expired. Click on the Input Data button to download all input data files. These contain the python scripts to run the simulation (macro.py, runme.py) and the settings from your local GeoDict that are automatically uploaded to ensure the same settings between local and cloud machine (e.g., your material database). If results are available for download, the Results button is active. Click it to download all result files in a zipped archive. The name of this archive is an automatically generated sequence of numbers and letters. Therefore, make sure to rename the folder for identification, if you download from the cloud web interface. The results contain the same files as described for directly downloading from GeoDict.

The Cloud Data panel lists all input and result ZIP files. They are named by an automatically generated sequence of numbers and letters. Therefore, you cannot identify if the ZIP file contains input or results and to which job these files belong. If you want to download input or result files, either do so directly from GeoDict or from the Jobs panel.