SCI Seg3D Mailing List

Text archives Help

Re: [Seg3D] Exporting segmentation out of original bounds

Chronological Thread 
  • From: Sander Land <>
  • To:
  • Subject: Re: [Seg3D] Exporting segmentation out of original bounds
  • Date: Mon, 8 Feb 2016 11:56:51 +0000

Hi Jess,

Somebody else created the project, and I'm not even sure how they got bits to be outside the image volume. Going back to the original project it looks like "mask layer -> transform". The "X" slice view does not go down further than the original volume either. Exporting to .nrrd and reading that in matlab has the same result as exporting to matlab.
I think the exporter is confused about the two layers not being aligned, but  I'd sort of expect the export function to export what I see on the screen regardless.
Anyway, starting over I don't see any options for extending or resizing a grid, where can I find this?


On Fri, Feb 5, 2016 at 7:18 PM, Jess Tate <> wrote:
Hi Sander,

There may be a couple of things going on here.  The simplest thing to check is to make sure that you are exporting and importing the right layers.  to create the segmentation 'out of bounds'  you needed to expand the grid, which it seems that you did.  Then you need to copy the entire layer to the new grid and save out the segementations from those new layers.  You can try right clicking on the desired layer to export it also.  

The matlab format from Seg3D doesn't save the spacial information, if I remember correctly.  That means if you have two volumes of different numbers of elements, one may be shifted depending on where the origin is supposed to be (as matlab will just set it to 0,0,0).  It could also be the wrong size depending on what the relative spacing is supposed to be.  


On Feb 5, 2016, at 4:09 AM, Sander Land <> wrote:

Hi Jess,

I am using File->Export Segmentation. Both 'to matlab' and 'to nrrd' have the same problem.
Here are some screenshots:
Image 1: `cap' visible outside image range.
Image 2: Exporting, see the cap is component 7.
Image 3: viewing in matlab, with hole clearly visible on the left.

As there does seem to be a component 7 in the matlab data, I've tried to see where it ends up, and turns out the problem is even worse than simple omission.
Component 7 gets translated to somewhere else in the volume and intersects with it, as shown here:
(output of figure(1); clf; isosurface( == 1,0.5); hold on; p=patch(isosurface( ="=7,0.5));set(p,'FaceColor','r');" axis equal)


On Thu, Feb 4, 2016 at 4:57 PM, Jess Tate <> wrote:
Hi Sander,

It’s a little tricky to understand what is going on, because when you export a segmentation, it should just save out the entire label mask.  Is it possible you are exporting the original image on accident?  You can try the 'Export Segmentation' option in the file menu, which has more controls than right clicking on the layer and exporting it that way.  If that isn’t working, a screen shot may help determine what is going on.


> On Feb 4, 2016, at 5:05 AM, wrote:
> I have an image data set which is missing a small part due to the bounds of
> the imaging. I've filled this in using the paint tool to make a smooth shape.
> However, when exporting the data set it's cut off again at the original
> bounds. Is there a way to extend these bounds and export the entire
> segmentation?
> Thanks,
> Sander

Archive powered by MHonArc 2.6.18.

Top of page