1
Python and Java API / 1.6.3 buildUV fallback to legacy paramterization
« on: June 24, 2020, 03:14:04 PM »
When performing the buildUV step, Metashape occasionaly restarts and falls back to legacy parameterization. This has quite an impact on total processing time.
What causes this? Is there a possibility to always use legacy parameterization so the processing time is consistent?
What causes this? Is there a possibility to always use legacy parameterization so the processing time is consistent?
Code: [Select]
chunk.buildUV(
mapping_mode=Metashape.MappingMode.values['GenericMapping'],
page_count=1,
)
Code: [Select]
[2020-06-24 07:18:17,854 ; INFO] Build UV progress: 77.5%
Pack iteration 0 ratio 0.525
[2020-06-24 07:18:23,612 ; INFO] Build UV progress: 78.4%
[2020-06-24 07:27:07,175 ; INFO] Build UV progress: 80.2%
Pack iteration 1 ratio 0.3875
[2020-06-24 07:37:03,775 ; INFO] Build UV progress: 82.0%
Pack iteration 2 ratio 0.31875
[2020-06-24 07:41:18,511 ; INFO] Build UV progress: 82.9%
[2020-06-24 07:47:38,643 ; INFO] Build UV progress: 84.7%
Pack iteration 3 ratio 0.284375
[2020-06-24 07:58:01,363 ; INFO] Build UV progress: 86.5%
Pack iteration 4 ratio 0.267188
[2020-06-24 08:08:07,043 ; INFO] Build UV progress: 87.4%
[2020-06-24 08:08:17,819 ; INFO] Build UV progress: 88.3%
done. (in 3000.14 sec)
Falling back to legacy parameterization
[2020-06-24 08:08:31,830 ; INFO] Build UV progress: 10.0%
[2020-06-24 08:09:36,172 ; INFO] Build UV progress: 10.9%
[2020-06-24 08:09:43,020 ; INFO] Build UV progress: 11.8%
[2020-06-24 08:09:59,182 ; INFO] Build UV progress: 12.7%
[2020-06-24 08:10:00,599 ; INFO] Build UV progress: 13.6%
[2020-06-24 08:10:10,627 ; INFO] Build UV progress: 14.5%
]2020-06-24 08:10:18,242 ; INFO] Build UV progress: 15.4%