Batch processing: Python

[maddin]

Would be great to be able to use Python code as part of the Batch Process pipeline, e.g. by inserting a "Run Python code" element into the batch queue?

[Alexey Pasumansky]

Hello maddin,

Run Script operation is already available in Batch Process dialog.

[maddin]

Run Script operation is already available in Batch Process dialog.

Doh! I was looking at the online help (which did not have that command listed) but indeed it is already in the Job type list, at the very bottom...

[Alexey Pasumansky]

Hello maddin,

It's also in the batch task list of the PhotoScan Pro manual, but also in the very end of the list.

[maddin]

It's also in the batch task list of the PhotoScan Pro manual, but also in the very end of the list.

Thanks!
Just to show that I did try to find this before posting: If you open the online help, type 'batch' into the search box, then select 'Automation' topic, you find a section called 'Batch processing' which has a list of operations, that does not contain any reference to running a script.

[Alexey Pasumansky]

Maybe you've accidentally opened Standard edition manual? I think that Run Script was available in the version 1.2 already and the information was also included in Pro edition manual.

But anyway it's sorted out now.

[maddin]

Maybe you've accidentally opened Standard edition manual? I think that Run Script was available in the version 1.2 already and the information was also included in Pro edition manual.

The information is indeed in the manual but not in the online help in .chm format.

[Thibaud Capra]

Is anything possible regarding the other way around?

I mean, can a "Run Batch" be part of a Python Script?

[Alexey Pasumansky]

Hello Thibaud,

Do you mean to import batch XML file via Python and treat it accordingly?

[Thibaud Capra]

Hello Alexey,

Any way would work, yes.

This mostly shows interest for version compatibility I'd say, when building the elements you need (Dense cloud, mesh etc.)

[Alexey Pasumansky]

Hello Thibaud,

The format of the XML file for the batch processing may change over time (when new arguments are added, for example), so the scripts may need the modifications when the newer versions are released.

So if the matter of the question is the need of scripts adapting to the newer releases, I don't think it would be solved, unless the development of Python API is freezed. At the moment we are trying to avoid major changes in API with the third number of PhotoScan release version, but with the second number there still could be some due to the changes in the internal representation fo the project, new features and functionality extension.

[Thibaud Capra]

Hello Alexey,

I did not consider possible changes in the XML format that may occur too, indeed.

Regarding script adaptation, is a backup compatibility possible? I mean, let 1.3 be able to fully read 1.2.x scripts, without making any change.

I'm using both versions depending on the workstation available, that's why I'm asking.

[Alexey Pasumansky]

Hello Thibaud,

When defining the set of the parameters for the processing functions you can use PhotoScan.app.version check and pass the parameters according to the actual version. Using scripts from the older versions is not always possible.

[Thibaud Capra]

Hello Alexey,

So you mean I could have a single script that'd call functions according to the PhotoScan.app.version return?
That'd be awesome!

What's the type of return? String?

[Alexey Pasumansky]

Hello Thibaud,

I mean something like the following:

Code: [Select]

if PhotoScan.app.version[:-2] == "1.1":
      ACCURACY = "High"
elif PhotoScan.app.version[:-2] in ["1.2", "1.3"]:
      ACCURACY = PhotoScan.Accuracy.HighAccuracy
else:
      print("Update PhotoScan")
      break

chunk.matchPhotos(accuracy = ACCURACY)