** Enter the path to the license file for Celantur here.
| export VERSION=23.09.1
bash celantur.sh --update
|
| ---------------------------------------------------------- |
Celantur version 23.09.1 is required
1. Create a Docker Compose file.\
Go to *${HOME}/.config/horus/celantur* and create a *docker-compose.yml* file. Give this file the following content:
| services:
celantur:
image: celantur-on-premise:23.09.1
ports:
- "7000:7000"
volumes:
- ${HOME}/.config/horus/celantur/licensing:/home/celantur/licensing
restart: always
deploy:
resources:
reservations:
devices:
- capabilities: \[gpu]
command: \["-l", "/home/celantur/licensing/license",
"--api", "0.0.0.0:7000",
"--api-endpoint", "http\://localhost:7000/",
"-a", "face",
"-a", "license-plate",
"-a", "person",
"-a", "vehicle",
"--format", "whole"]
|
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
1. Start the new Celantur container.
| cd ${HOME}/.config/horus/celantur |
| --------------------------------- |
| docker compose up -d celantur |
| ----------------------------- |
Give the Container some time to start (\~20s), you can verify if the container is running with the following command:
| curl -X GET |
| --------------------------------------------- |
If the container is running a ‘System Running’ message will be printed to the Command Line.
#### **2.4** Deploying Horus System V2
1. Copy the “Horus\_Linking\_Lab-\*-x86\_64.AppImage” to the system.\
If you do not have this file, contact
2. Mark the .AppImage as executable
This can be done via the *File Manager*.\
Open the *File Properties* of the file and enable the *executable* setting.
Alternatively, this can also be done via the Command Line.\
Open a command line and locate the .AppImage.\
To give executable permission to the file enter the following:
| chmod +x \ |
| -------------------------------- |
\
Verify that the file now has executable permissions by entering:
| ls -l \ |
| ----------------------------- |
\
The file should now have the same permissions as shown on the image below.
1. Start the “Horus\_Linking\_Lab-\*-x86\_64.AppImage”
2. A window will open with the connection screen, select ‘This System’ to continue.
3. On the Main Menu open the License Manager.\
Enter the received License Key.\
Verify that the required components are now licensed via ‘List of License Components’.
The system is now ready for Batch Processing.
### **3.** Starting a Batch Job
1. Verify that the Celantur blurring service is running.\
See step 7 chapter 2.3 on how to verify this.
2. Start the “Horus\_Linking\_Lab-\*-x86\_64.AppImage”.
3. Connect to ‘This System’.\
4. Open the ‘Batch Processing’ tool on the main menu.\
5. Select ‘New Job’ to start a batch job. 
1. Select a process\
\- Blur JPEG Images\
\- Blur PGR Images\
\- Generate frames.xml from EXIF Metadata\
2. Select a pipeline\
\- Blurring vehicles and people\
\- Blurring license plates and faces\
This setting is only used for blurring.
3. Source folder\
Define the path of the parent directory where the recordings are stored.
4. *create a job for each sub-folder of the source*\
Choose to create a separate batch job for each descendant sub-folder of the source location.
5. Destination folder\
Define the path to the location where the new data will be written to.
For the ‘Frames.xml from Exif’ process we recommend saving the output to the source directory.
6. Start new job\
Press on the blue ‘start new job’ button to add the batch job to the queue.
6. Monitor the status of the batch job.
If there are no pending jobs currently being processed or in the queue, then the new job will automatically start processing.
By selecting a batch job, you can view additional information about the processing.
If you are unsure if the batch job is being processed, you may open the Graph Builder and verify if the pipeline is running and processing data.
When the processing is done the job will be marked as completed.
7. Check the output of the batch job.\
Verify that the process has correctly processed the data by checking the destination folder.\
Verify that vehicles and/or persons are now blurred, or that a frames.xml is created.