Forum

Author Topic: Export fails in cluster if path contains variables  (Read 2999 times)

calculon

  • Newbie
  • *
  • Posts: 3
    • View Profile
Export fails in cluster if path contains variables
« on: March 09, 2022, 05:07:29 PM »
We run batch processes in cluster and found, that TIF exports of DEM and ORTHO does not work.
The reason seems to be variables in the output paths, absolute paths work as expected.
There is no error messages or other indications of fail, the process simply does not yield expected results.

Here is the diff between our non-workin and working versions (absolute paths work via cloud, the others not):

diff ms_batch.xml tmp.debug_ms-tiffexportcloud.xml
61c61
<     <path>{projectfolder}/dem_{chunklabel}.tif</path>
---
>     <path>/data/tmp-data/dem_debugout.tif</path>
81c81
<     <path>{projectfolder}/ortho_{chunklabel}.tif</path>
---
>     <path>/data/tmp-data/ortho_debugout.tif</path>

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 14813
    • View Profile
Re: Export fails in cluster if path contains variables
« Reply #1 on: March 10, 2022, 11:52:55 PM »
Hello calculon,

Have you checked, if the batch defined in a similar way works for the project processed locally?

And also please try to leave only {chunklabel} macros in the network processing batch - does it work as expected, if the project path is input without {projectfolder} macros?
Best regards,
Alexey Pasumansky,
Agisoft LLC

calculon

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Export fails in cluster if path contains variables
« Reply #2 on: April 13, 2023, 12:52:24 PM »
In case anyone is facing a similar problem:

We recently managed to fix it by using <path>/{projectfolder}/dem_{chunklabel}.tif</path> in our batch file.
The first slash seemed to make the difference for us.