I am encountering an issue where tasks submitted for batch processing through both the Metashape GUI and Python scripts do not initiate. The core of the problem seems to be that no workers are assigned to the tasks, showing a status of 0/0 workers, regardless of the submission method. This occurs during the following process:
1. In the Metashape GUI, I navigate to Workflow -> Batch Process -> Add -> Run Script, then select any file and submit it to the network. However, the task does not start due to 0/0 workers being assigned.
2. Similarly, when submitting a Run Script task via Python, the same issue of 0/0 workers being assigned is observed.
I found a temporary workaround by exporting the batch tasks from the monitor, manually editing the XML to set the worker count to 1, and then reimporting it. After this manual adjustment, the script processes as expected.
I am inquiring if there exists a more streamlined workaround or a feature that allows for the direct submission of tasks with scripts over the network. Specifically, is it possible to submit custom JSON or XML directly to the Metashape server, bypassing the need to use the RunScript() function?
Additionally, it would be immensely beneficial if there was a way to specify the number of workers when submitting a script for batch processing. Ideally, setting this number to, for example, 3, would enable the script to run in parallel across three machines. This would not only bypass the limitation of restricting a batch script to a single machine but also enhance efficiency by leveraging parallel processing capabilities. The logic for parallel processes could be embedded within the Python script itself, necessitating only the addition of a parameter to dictate the desired number of executions.