ikolesov / kslice Goto Github PK

I commented out certain functions whose presence is unnecessary. PK, search for comments in the project 'PKDelete' and either uncomment the function (if its essential) or delete the section

UIVol and UIArray are not sync'd necessarily, leads to bizarre effects when trying to switch between 2d/3d or uk at a point

range_UIVol = self.UIVol.GetScalarRange()
range_UIArr = [self.UIarray.min(),self.UIarray.max()]

print the ranges:

''''
Accumulate User Input! [252, 189, 73]Axial (Red)
modified by user, kslice bot is running
min,max of UIVol and UIArr = (-1.0, 0.0); [-6.0, 0.0], sign(uk)= -1
''''

if the input is char/uchar, crash with read error

if it is wrong signed-ness short or float32, double64, weird obscure things happen with no warning.

This block has a flawed assumption; modfied happens in many situations, not necessarily drawing! Eg: switch modules, resize window, etc.

'''''
#put a listener on label, so we know when user has drawn
labelImg=self.labelNode.GetImageData()
self.ladMod_tag=labelImg.AddObserver("ModifiedEvent", self.labModByUser)
self.labelImg=labelImg
'''''

This is a built in feature in Slicer (toggle to erase using 'd' ) but it's broken currently, when will it be fixed?

Why must the library be copied to the Slicer bin directory for slicer to discover it despite having added the original location of the library to the slicers modules path?

We want to wait for user to finish his brushstroke (rather than looking at each brush circle at a time for instance) to compute the nex user input. To what event should the observer respond for this to occur?

We were told to call modify 2x (once in python after changes, once in vtkKSlice in runUpdate() function) this results in observers listening to Modified events being called twice. thus the call in runUpdate() has been commented out (will this break anything down the road?). Look at function labModByUser() in python code, is this the correct way to discriminate between events when label was modified by user vs when the active contour changed the label (necessary to know this for using a cached level set vs re-initializing it)?

Given various formats of images ( I,j,k coordinates can correspond to different directions saggital, coronal, axial) how to pull out right slice in the volume?

file -> new scene, but kslice instance keeps running in the background?

something bad is going to happen, unless maybe you reload the same image (?)

Why is it necessary to copy vtkKSlice.cpp(h) to the Logic directory, why don't relative paths (commented out) work?