Get3D Engine
Get3D Engine is a work module, running in the background processing tasks, can be online cluster processing jobs.
Last updated
Get3D Engine is a work module, running in the background processing tasks, can be online cluster processing jobs.
Last updated
Get3D Engine features a monitoring function for quickly checking engine status, utilization, and modifying settings. Users can adjust configurations such as the "job queue directory," "cache directory," "engine capabilities," and control the engine with "start/stop" options.
Job Queue Directory: Defines the job path of the current project, the jobs submitted by the current project are stored under this path, waiting for the engine to accept the processing.
Cache Directory: Stores temporary files during job processing, the path needs to be set to the local disk.
In the Get3D Mapper main interface, the Job Queue Directory is used to store submitted jobs. The Get3D Engine retrieves jobs submitted by Get3D Mapper from the Job Queue Directory. The engine reads job information (e.g., AT_job/Reconstruction_job), processes the jobs, and outputs the results.
The Engine Monitoring Panel at the bottom of Get3D Mapper displays the job queue and engine status.
Job Queue Directory
Current job queue directory, where the project's jobs are stored.
Engines
The number of engines in the current job queue directory.
Running Engines
The number of running engines in the current job queue directory.
Refresh
Refresh engine status。
Job Queue Setting
Set the job queue for project. Cannot be changed when engine is running.
Engine Setting
Set the job queue for the engine to receive jobs.
View Engine Status
Check the status of running jobs of engines in the current project.
Start Local Engine
Start the local engine.
Local Engine
The status of the local engine includes four states:s:
None: Engine is not started. Pending: Engine is waitng to accept jobs.
Running: Engine is processing jobs
Inconsistent path: The engine's job queue directory differs from the project job queue.
Get3D Engine interface has two module: Engine Information and Engine Log
The Engine Information module contains host name, IP address, engine version, engine status, engine capability, job queue directory, cache directory, cache space, CPU utilization, memory utilization, and GPU memory utilization.
Host Name
Device name
IP Address
Device IP address
Engine Version
Get3D Engine version
Engine Status
Stop(closed), Waiting(opened without accepting a task), Running(task running), Abnormal (exited abnormally)
Engine Capability
Set the engine capability, the engine only processes jobs with this processing capability. AT: extract points, matching, small block bundle, overall bundle; Reconstruction
Job Queue Directory
Set directory for engine to receive jobs
Cache Directory
Set engine cache directory
Cache Space Remaining
Project cache disk, used space/hard drive space
CPU Utilization
CPU usage percentage
Memory Utilization
Memory, used memory/node memory
GPU Utilization
Video memory, used video memory/node video memory
The engine setting function is in the node information list, right-click to jump out, the setting function is shown in the figure below:
Refresh Engine Information
Refresh engine CPU, memory, GPU utilization, engine status, cache directory space remaining information
Modify Job Queue Directory
Modify the job queue directory of engine
Modify Cache Directory
Modify the cache directory of project
Set Engine Capabilities
Acquire the capability to receive AT/reconstruction jobs
Start Engine
Start accepting jobs
Stop Engine
Stop accepting jobs
