djelouze / chiron Goto Github PK

This occurs when 2 Chiron views are opened. The volume is visible in the first one #1, but invisible in the second one #2. Right click on #2 in order to choose "Slice volume" with volume selected in the pipeline browser ends with a seg fault.

:D,

I used part of its algorithm to make an overview of a volume[1]. But I found that the binormal alter the direction along the cut, with that solved by making the dot product of the binormal to the current point of my curve cut, if less than zero then I change the cross product of [tangent x normal] By binormal = [normal x tangent] = binormal, and the binormal not change the direction of the court[2].

[1] - http://code.google.com/p/moonstonemedical/source/browse/src/moonstone/ilsa/plugins/reslice/gui/qt/resliceaction.py

[2] - http://code.google.com/p/moonstonemedical/source/browse/src/moonstone/ilsa/plugins/reslice/gui/qt/resliceaction.py#1144

So long and good luck,
Nycholas de Oliveira e Oliveira.

The built-in action "Link camera" is proposed after the Chiron contextual menu (right click)

As soon as the user initiate a new spline, ParaView crashes. Release only.

in chrContourTracer::keyPress at Chiron/Modules/chrContourTracer.cxx:151

Hello!
I'm trying to get panoramic view of a volume (on vtk) using your class vtkStraightenedCurvedPlanarReformation. But I don't know exactly how it works, could you please post a small example? Or give a detailed description on how should be done?

Many thanks

Step to reproduce:

• Activate "Contour Tracer"
• Add few points (ctrl+click)
• Delete the current SplineSource from the pipeline browser
• Add a point (ctrl+click)
  -> segfault

Readers XML have to include the following element in SourceProxy:

  <Hints>
    <ReaderFactory extensions="dcm"
                   file_description="Dicom Directory" />
 </Hints>

simply add view->render() at the end of Activate()

Not only it doesn't window/level as expected, but even after hiding the scalar bar and Activating/Deactivating the Module a no effect. Workaround is to close the view and reopen a new one