update crop coordinate fields in worker communication protocol to support rectangular cropping
	
		
			
	
		
	
	
		
	
		
			All checks were successful
		
		
	
	
		
			
				
	
				Build Backend Application and Docker Image / build-docker (push) Successful in 11m5s
				
			
		
		
	
	
				
					
				
			
		
			All checks were successful
		
		
	
	Build Backend Application and Docker Image / build-docker (push) Successful in 11m5s
				
			This commit is contained in:
		
							parent
							
								
									8e14897a69
								
							
						
					
					
						commit
						39d49ba617
					
				
					 1 changed files with 10 additions and 6 deletions
				
			
		
							
								
								
									
										16
									
								
								worker.md
									
										
									
									
									
								
							
							
						
						
									
										16
									
								
								worker.md
									
										
									
									
									
								
							| 
						 | 
				
			
			@ -59,15 +59,17 @@ This message is crucial for the backend to monitor your worker's health and stat
 | 
			
		|||
      "modelId": 101,
 | 
			
		||||
      "modelName": "General Object Detection",
 | 
			
		||||
      "online": true,
 | 
			
		||||
      "cropX": 100,
 | 
			
		||||
      "cropY": 200
 | 
			
		||||
      "cropX1": 100,
 | 
			
		||||
      "cropY1": 200,
 | 
			
		||||
      "cropX2": 300,
 | 
			
		||||
      "cropY2": 400
 | 
			
		||||
    }
 | 
			
		||||
  ]
 | 
			
		||||
}
 | 
			
		||||
```
 | 
			
		||||
 | 
			
		||||
> **Note:**
 | 
			
		||||
> - `cropX` and `cropY` (optional, integer) should be included in each camera connection to indicate the initial crop coordinates for that subscription.
 | 
			
		||||
> - `cropX1`, `cropY1`, `cropX2`, `cropY2` (optional, integer) should be included in each camera connection to indicate the crop coordinates for that subscription.
 | 
			
		||||
 | 
			
		||||
### 4.2. Image Detection
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			@ -180,14 +182,16 @@ Instructs the worker to process a camera's RTSP stream using the configuration f
 | 
			
		|||
    "modelUrl": "http://storage/models/us-lpr.mpta",
 | 
			
		||||
    "modelName": "US-LPR-and-Vehicle-ID",
 | 
			
		||||
    "modelId": 102,
 | 
			
		||||
    "cropX": 100,
 | 
			
		||||
    "cropY": 200
 | 
			
		||||
    "cropX1": 100,
 | 
			
		||||
    "cropY1": 200,
 | 
			
		||||
    "cropX2": 300,
 | 
			
		||||
    "cropY2": 400
 | 
			
		||||
  }
 | 
			
		||||
}
 | 
			
		||||
```
 | 
			
		||||
 | 
			
		||||
> **Note:**
 | 
			
		||||
> - `cropX` and `cropY` (optional, integer) specify the initial crop coordinates for the camera stream. These values are configured per display and passed in the subscription payload. If not provided, the worker should process the full frame.
 | 
			
		||||
> - `cropX1`, `cropY1`, `cropX2`, `cropY2` (optional, integer) specify the crop coordinates for the camera stream. These values are configured per display and passed in the subscription payload. If not provided, the worker should process the full frame.
 | 
			
		||||
>
 | 
			
		||||
 | 
			
		||||
> **Important:**
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue