- Fixed the range of the "previewSize" parameter: since its step was set
to 5000, it could only be set to 0 or 1000. It can now be set from 0 to
5000 with steps of 100 pixels;
- Fixed the case of the "previewSize" and "outputPanoramaPreview";
- Improved the description of "previewSize", and added descriptions for
"outputPanorama" and "outputPanoramaPreview".
The GPU's name was never retrieved, meaning that whenever a GPU was
found, all its information was displayed, except for its name, although
it was expected on the QML side.
This commit fixes this issue.
- `meshroom_submit`: the submission to the render farm is now effective
(the script did not work at all).
- `meshroom_status`: the `--toNode` option did not work and caused errors.
- `meshroom_statistics`: some adjustments needed to be made for the script
to run with Python3 instead of Python2, an issue in the core/stats.py file
led the `statistics` file to never being read correctly, and the calls
to the Matplotlib API were outdated.
When reading the `ComputerStatistics` and `ProcStatistics` from a file
(and thus from a dictionary), the `computer` and `process` objects need
to be correctly initialized as `ComputerStatistics` and `ProcStatistics`
objects. Otherwise, they cannot access their `fromDict` method and will
remain empty dictionaries.
Add two new input parameters, `nbFirstUnstableCameras` which sets the
number of cameras for which a bundle adjustment is performed every time
a camera is added, and `maxImagesPerGroup` which sets the maximum number
of cameras that can be added before the bundle adjustment has to be
performed again.
By default, the bundle adjustment will be performed every time one of
the first 30 cameras is added, as computations are not too expensive
while there are few cameras. Past that number, the bundle adjustment will
only be performed when up to 30 cameras have been added.
The node's version is updated accordingly.
This commit updates the name of the input parameter (from "mediaPaths" to
"inputPaths") as it now also supports SfMData files, and adds two SfMData
files as output parameters: one that contains the selected keyframes, and
one that contains the frames that were not selected as keyframes.
Version objects were meant to be used only with numerical characters,
separated by periods. Now that the version of Meshroom can also contain
its status ("develop" when it is in develop mode), the Version class
needs to be able to parse the status string as well as the version
components when it exists.
The status is handled as a separate string, which is returned in addition
to the tuple of integers when the whole version string is parsed in the
first place.
This prevents issues when opening files that have been saved with a version
like "x.x.x-develop".
If a compatibility issue is found and the assertion is raised, a message
is now displayed to indicate which template (with its path) and which
node (with its node type) caused the issue.
