Sub-tasks Inquiry

Hello,

When I test my algorithm against 3 images, it return correctly the 3 segmentation output images but return only 2 files for the sub-tasks the first one is "aortic-vessel-tree.obj" and the second is "aortic-vessel-tree-volume-mesh.obj" not even knowing for which image it produced, it is because the saving path is static not dynamic as the path of the segmentation output is dynamic depending on the image name, I think it should return for every image a segmentation output image and "aortic-vessel-tree-.obj" and the second is "aortic-vessel-tree-volume-mesh-.obj".

Please correct me if i'm wrong. Thank you.

Hi,

do not worry about this as there is one more level of abstraction. The structure was decided by the Grand-Challenge team. The platform will know how to store the file when you use the interface /output/aortic-vessel-tree.obj If you use a different path/filename, it will raise an error.

Best, Antonio

Hello,

Thank you for your response. I have another question I submitted the mesh obj but still the mean_jacobian -100 for both images, however, after uploading the container and trying out the algorithm the mesh obj is created and can be visualized and "vis_available" key is set to True.

Hi,

a Mean Jacobian of -100 is a placeholder for us -- it means that you did not submit a solution for the subtask on volumetric meshing.

"vis_available" true means that you submitted a solution for the visualization subtask.

The meshing task requires a surface mesh that can be meshed with TetGen with params "-pq" (default parameters in MeshPy.tet)

Best Antonio

Hi, we also have the same problem with -100. We create a mesh with trimesh and return it to the position of the initial simple box mesh. However, I checked also a submission with the primitive box in the position of meshes and the mean scaled jacobian was also -100. Are there any other requirements apart from the submission of a trimesh object?

Hi,

Converting the segmentation to a surface mesh (e.g. marching cubes) is not sufficient for the volumetric subtask.

Is your output watertight?

My recommendation is to ensure that the output is watertight and then check locally how meshpy behaves on your outputs locally.

Best Antonio