Open liuyx599 opened 11 months ago
Hi! Yes, this is a common problem with a fix. There's a reliability tradeoff since to fix it, we have to ignore missing file errors and autofill them with black. In practice, it's been fine for a few years, but we have seen some missing tiles years ago in earlier versions of the software when used at huge scale.
To fix this, generate your tasks with the --fill-missing
flag. e.g.
igneous mesh forge $segdir --dir mesh --mip 2 --queue $meshforge_queue --sharded --fill-missing
igneous skeleton forge $segdir --mip 2 --queue $skelforge_queue --scale 4 --const 100 --sharded --fill-missing
Happy meshing and skeletonizing!
Hi, I recently generated mesh and skeleton for the segmentation results of a larger electron microscopy dataset, and I used the following commands:
Generate mesh:
Generate skeleton:
When running the command
igneous execute
, the same error seems to occur in both scripts:The staus of
$skelforge_queue
Then, I try to access the autoseg data by CloudVolume
The same error seems to have occurred
The
cv.meta.info
of the autoseg(mip=2) isI was observing the region Bbox([15940, 40089, 18946],[16004, 40153, 19010] on Neuroglancer and it seems to be at the edge of the entire electron microscopy dataset now. It is indeed a dark patch with no segmentation results.
In large-scale electron microscopy datasets, such as FAFB, MiCrONS, H01, etc., the vast majority of neuron segmentation results are in the middle region of the dataset, and it seems to be not uncommon to have no segmentation results in the edge region.
I'm wondering if there is another way to avoid this error, and I'm wondering if
cloudvlomue
, origenous
, has a relevant api parameter that defaults empty regions to 0 when accessed, which might avoid the above EmptyVolumeException.