Unexpected PointCloudGroundTruth folder is created with geom pipe on real plant

[fabfabBesnard]

Using geom pipeline with v0.10: an unexpected folder called "PointCloudGroundTruth_100000__VirtualPlantObj_5e491f1cff" is created the folder is empty. However, there is no virtual plant in the analysis, so no possible virtual groundtruth (for the pcd or any other 3D objects)

[fabfabBesnard]

PointCloudGroundTruth_100000__VirtualPlantObj_5e491f1cff task recorded the following parameters metadata:

{
  "task_params": {
    "pcd_size": 100000,
    "scan_id": "",
    "upstream_task": "VirtualPlantObj"
  }
}

In the log file of the run, only the task Visualizationis mentioning virtual object:

[pid 5521] Worker Worker(salt=100622210, workers=1, host=bd297c23f5bb, username=scanner, pid=5521) done      Visualization(scan_id=, upstream_point_cloud=PointCloud, upstream_mesh=TriangleMesh, upstream_colmap=Colmap, upstream_angles=AnglesAndInternodes, upstream_skeleton=CurveSkeleton, upstream_images=ImagesFilesetExists, query={}, upstream_virtualplantobj=VirtualPlantObj, upstream_pcd_ground_truth=PointCloudGroundTruth, upstream_pcd_evaluation=PointCloudEvaluation, upstream_segmentedpcd_evaluation=SegmentedPointCloudEvaluation, upstream_segmentation2d_evaluation=Segmentation2DEvaluation, use_colmap_poses=True, max_image_size=1500, max_point_cloud_size=100000, thumbnail_size=150) from fileConfig

But in the submitted config (.toml), there is no such parameter in the section of the [Visualization] task:

[Visualization]
upstream_point_cloud = "PointCloud"
upstream_mesh = "TriangleMesh"
upstream_colmap = "Colmap"
upstream_angles = "AnglesAndInternodes"
upstream_skeleton = "CurveSkeleton"
upstream_images = "ImagesFilesetExists"
max_image_size = 1500
max_point_cloud_size = 100000 #test: modified to improve pcd visualization in plant-3d-explorer. default was 10000
thumbnail_size = 150

[fabfabBesnard]

Another weird behavior may be linked to this issue: when running visualization, all folders up to AnglesAndInternodes are created (potentially empty) even if the task has not been run in the pipe.