Meshroom/bin
Candice Bentéjac 1f75ccaf5f [bin] meshroom_batch: Save graph once it has been all set up and resolved
If the "save" argument has been provided, the graph should be saved
outside of the `GraphModificatioǹ event, once it has been set up entirely
and resolved.

When it is saved within the `GraphModification`, UIDs are not yet
available.

This does not cause any issue for the rest of the execution if the graph
is to be computed locally, since the UIDs will be computed right
after (but the UIDs will still never be written in the project file).
However, when submitting the graph to a renderfarm, the project file is
loaded again. If it does not contain any UID:
 - all the nodes will present the `UidConflict` compatibility issue
 - key errors will be raised when trying to apply the links between nodes
since they contain direct references to UIDs, which cannot be resolved as
they are not present in the project file.
2023-06-30 18:59:32 +02:00
..
ion_start_meshroom.sh update ion startup 2022-11-04 13:54:32 +01:00
meshroom_batch [bin] meshroom_batch: Save graph once it has been all set up and resolved 2023-06-30 18:59:32 +02:00
meshroom_compute [core] do not use the task manager in batch command line tools 2021-10-19 15:48:07 +02:00
meshroom_newNodeType [bin] newNodeType: update 2022-02-22 15:35:37 +01:00
meshroom_statistics [bin] Fix all the scripts that had errors 2023-04-24 16:43:01 +02:00
meshroom_status [bin] Fix all the scripts that had errors 2023-04-24 16:43:01 +02:00
meshroom_submit [bin] Fix all the scripts that had errors 2023-04-24 16:43:01 +02:00