Page MenuHomePhabricator

Errors when using ImageStatistics after AutoCropping a segmentation
Closed, InvalidPublic

Description

  • Create segmentation
  • select image statistics
  • select auto crop
  • try to update image statistics.

Errors appear in the image statistics view and on the log output:

623.08 sb.bun.imgStat.view: Retrieving StatisticsCalculator
651.79 ext.bun.seg.view: Node 'Kidney' selected
651.79 ext.bun.seg.view: Working image 'Kidney' selected
651.81 ext.bun.seg.view: Reference image 'Pic3D' selected
651.81 ext.bun.seg.view: Reference 00000000074934F0 Working 0000000007492EF0
651.82 ext.bun.seg.view: Updating alignment warning
651.85 ext.con.segInterpolationcontroller ERROR: original patient image does not
match segmentation (different extent in dimension 0), ignoring patient image
651.87 ext.con.segInterpolationcontroller ERROR: original patient image does not
match segmentation (different extent in dimension 0), ignoring patient image
651.98 sb.bun.imgStat.view: Retrieving StatisticsCalculator
651.98 ext.bun.dataMng.view: changed
651.99 ext.bun.dataMng.view: changed
652.15 sb.bun.imgStat.view ERROR: Caught exception: ..\..\..\..\source\ITK3160\C
ode\Common\itkMultiThreader.cxx:475:
itk::ERROR: MultiThreader(00000000187FD800): Exception occurred during SingleMet
hodExecute
v:\windows\source\itk3160\code\common\itkImageConstIterator.h:182:
itk::ERROR: Region ImageRegion (0000000000AA9900)

Dimension: 3
Index: [0, 0, 0]
Size: [256, 256, 13]

is outside of buffered region ImageRegion (00000000075706E0)

Dimension: 3
Index: [0, 0, 0]
Size: [48, 57, 22]

732.81 ext.bun.seg.view: Ignore this selection event: sourcepart == this 0 selec
tion == NULL1
732.82 sb.bun.imgStat.view: Retrieving StatisticsCalculator
740.73 ext.bun.seg.view: Node 'Kidney' selected
740.73 ext.bun.seg.view: Working image 'Kidney' selected
740.74 ext.bun.seg.view: Reference image 'Pic3D' selected
740.76 ext.bun.seg.view: Reference 00000000074934F0 Working 0000000007492EF0
740.76 ext.bun.seg.view: Updating alignment warning
740.81 ext.con.segInterpolationcontroller ERROR: original patient image does not
match segmentation (different extent in dimension 0), ignoring patient image
740.88 sb.bun.imgStat.view: Retrieving StatisticsCalculator
742.31 ext.bun.seg.view: Node 'Pic3D' selected
742.32 ext.bun.seg.view: Reference image 'Pic3D' selected
742.32 ext.bun.seg.view: Reference 00000000074934F0 Working 0000000000000000
742.34 ext.bun.seg.view: Updating alignment warning
742.35 ext.bun.seg.view: Only reference selected, re-show all its child segmenta
tions
742.49 sb.bun.imgStat.view: Retrieving StatisticsCalculator
743.29 ext.bun.seg.view: Node 'Kidney' selected
743.29 ext.bun.seg.view: Working image 'Kidney' selected
743.31 ext.bun.seg.view: Reference image 'Pic3D' selected
743.32 ext.bun.seg.view: Reference 00000000074934F0 Working 0000000007492EF0
743.32 ext.bun.seg.view: Updating alignment warning
743.35 ext.con.segInterpolationcontroller ERROR: original patient image does not
match segmentation (different extent in dimension 0), ignoring patient image
743.38 ext.con.segInterpolationcontroller ERROR: original patient image does not
match segmentation (different extent in dimension 0), ignoring patient image
743.56 sb.bun.imgStat.view: Retrieving StatisticsCalculator

Event Timeline

ok, this reads like it is unrelated to statistics, complaints come from the interpolation which assumes equal sizes of reference and working image (should not be necessary)

Just because I don't have a working binary available.. does this describe a crash, a malfunction or just some annoying logging output?

I cannot reproduce this error anymore. Seems to be fixed by now.

kislinsk changed the task status from Invalid to Spite.Jun 27 2018, 1:33 PM
kislinsk added a project: Bulk Edit.
kislinsk changed the task status from Spite to Invalid.Jun 27 2018, 1:37 PM
kislinsk removed a project: Bulk Edit.