🗺️3.2 Get3D Engine

Get3D Engine is a work module, running in the background processing tasks, can be online cluster processing tasks.

Get3D Engine is a work module, running in the background processing tasks, can be online cluster processing tasks. Get3D Engine has a monitoring function, support for quickly check the engine status, engine utilization, and you can quickly modify the engine status, adjustments and settings through the setting of "local engine monitoring directory", "cache directory", "engine capacity", engine "start/pause", and so on. Get3D Engine is equipped with monitoring function, which supports to quickly check engine status, engine utilization, and quickly modify engine status, adjustment and settings by setting "local engine monitoring directory", "cache directory", "engine capacity", engine "start/pause".

3.2.1 Principles of Operation

• Task Directory: defines the task path of the current project, the tasks submitted by the current project are stored under this path, waiting for the engine to accept the processing, i.e. a folder storing the tasks.

• Local Engine Monitor Directory: Define the path for local engine to get the tasks, i.e. the local engine monitor directory is specified under a folder for storing the tasks.

When the local engine monitor directory is specified in the same folder as the task directory of a project, the engine will process the tasks in this project.

• Project cache Directory: stores temporary files during task processing, the path needs to be set to the local disk.

Get3DMapper main interface set "Task Directory", the submitted tasks are stored in the "Task Directory"; Get3DEngine set "Engine Monitor Directory Get3DEngine sets "Engine Monitor Directory", in this directory, the engine gets "tasks submitted by Get3DMapper and stored in the task directory", Get3DEngine reads the task information (AT_job/Reconstruction_job), processes the task and outputs the The result.

3.2.1.1 Get3D Engine Interface

Get3D Engine engine interface, node information list, engine log two modules.

The node information list module contains host name, IP address, engine version, engine status, engine capability, task directory, engine cache directory, cache space, CPU utilisation, memory utilisation, GPU memory utilisation.

Function Name	Explanation
Host Name	Device Name
IP Address	Device IP Address
Engine Version	Engine Version
Engine Status	Not started (closed), Waiting (opened without accepting a task), Running (task running), Exception (exited abnormally)
Engine Capability	Set the engine capability, the engine only processes tasks with this processing capability.Empty three: lifting point, matching, small block leveling, overall leveling;Reconstruction；
Monitor Directory	Set monitoring directory
Engine Cache Directory	Set engine cache directory
Cache Directory Space Remaining	Project cache disc, used space/hard drive space
CPU Utilization	cpu occupancy percentage
Memory Utilization	Memory, used memory/node memory
GPU Memory Utilization	Graphics memory, used graphics memory/node graphics memory

3.2.1.2 Get3D Engine Setting

The engine setting function is in the node information list, right-click or multi-select and then right-click to jump out, the setting function is shown in the figure below:

Get3D Engine Settings Description:

The functions in the engine settings all support single operation or multi-select batch operation.

① Setting Multi-Open Function Interface

In the multi-open setting interface, set the "number of multi-open" to control the engine multi-opening.

② Setting Engine Capability Function Screen

Checking the box indicates that the acquisition and processing capability of the task is set.

Function Name	Explanation
Refresh Engine Information	Refresh engine CPU, memory, GPU utilization, engine status, cache directory space remaining information
Setting Engine Capabilities	Gain the ability to receive empty/rebuilt tasks
Modifying the Task Directory	Modify the task directory for engine monitoring
Modify Cache Directory	Modify the cache storage directory
Setting up Multiple Openings	Accept multiple tasks on a single machine at the same time, with a maximum of 4 supported.
Starting the Engine	Start accepting tasks
Stop Engine	Stop accepting tasks

3.2.2 Usage Example

The following paths are all custom paths and can be replaced by any other paths. It should be noted that all nodes should be on the same LAN when processing tasks in the cluster, and the "original image", "project directory" and "project task directory" should be accessible and readable by every device in the cluster. The "Original Image", "Project Catalogue" and "Project Task Catalogue" need to be accessible by every device under the cluster.

1. Create a new G3D project Select the project path:\\10.100.6.100\sharebuf\G3DProject

2. Task Directory Settings Set the project "task directory": \\10.100.6.100\sharebuf\job

3. Montor Directory Setting Set "engine directory": \\10.100.6.100\sharebuf\job Start the engine

Set "engine directory": \\10.100.6.100\sharebuf\job, Start the engine.

Set "Cache Directory": D:/cache

Set "number of engines": 2.

After setting, click "Start Engine".

4. Submitting aerial triangulation tasks

5. Other engine settings

Open the other node engine and set the monitoring directory: \\10.100.6.100\sharebuf\job

Change the engine status from "Waiting" to "Running";

Check the information in the lower left corner of the main interface, number of engines: 2; number of engines running: 2.