Spline\Polyline entities: fixed the defect when the control point is selected, moved outside the document area and becomes unreachable.

Added the menu item   MainMenu>Trace>MagTrace

Implemented a support function to output the Edges used by MagTrace for the current slice.
Currently selected MagTrace parameters are used so it is a 1-click operation.

Corrected the "HitTest" on mouse click over the Spline entity.

Corrected the defect for the HitTest mouse click on the polyline.

Modified the ToolTip for the "Width\Level" button of the Main toolbar.

Added   "MainMenu>Trace>Application specific settings" ability for {Femur,Hippocampus} applications.

MagTrace tool: implemented 2 new UI-level functions
a) Snap Selection to Image
b) Copy from adjacent slice and Snap to image.

MagTrace on Hippocampus.

First experiment:  To evaluate the quality of snapping, I used the supplied HC Roi as the guidance.  I clicked precisely on the boundary of the HC-ROI and let the software to adjust the position.
Attached screenshot shows the snapped points, without any manual further corrections.
Note: the snapping was performed on x3 upsampled resolution (EMD\Radial\2.2).

MagTrace:  Restart tracing> fixed the Bug when user had polyline selected on a different slice from currently  MagTrace operational slice.

FireVoxel Build 211 is released.

1.  First version and user interface for the MagTrace semi-automatic tracing functionality.

MagTrace tool:  implemented functionality to resume the tracing of the existing Spline
a) Select the desired spline
b) Press MagTrace button.  Operation will resume from the last point.

Magtrace tool:  prevented the "Double entry" error when user presses snap button before the previous snap operation is finished.

MagTrace tool:  fixed crash when the user clicks within the document window, but not on the image.

PolyTool\MagTrace tool:  don't perform any action if the mouse cursor is out of client are.
(affected:  MouseMove and MouseLButtonDown)

MagTrace: implemented various support function for Splines:
a) UpdateRectangle calculation
b) Spline contour hit test.

Implemented the Spline\Polyline rasterization function.
Several contours and\or holes are allowed.
Spline - polygons could be mixed.
Internally this supports 2.5D polygons (i.e. 2D+SliceIndex).

Created new C++:CDrawTool  "Magnetic Trace" and added a corresponding menu item to avoid cluttering the Polygon functionality.

Improved the semi-automatic "Snap-To-Point" function and corresponding UI.
This is mostly due to better matching and usage of Splines.

Initial pass: user quickly clicks on desired location and proceeds WITHOUT correction

On the second, manual pass, user simply drags the control points (about 5-6) in this example and contour adjusts.

Implemented general  Cubic Hermite Splines 2D function.  It supports several types of splines {CARDINAL,FinalDiff,Catmull-ROM}
The challenge was to implement it so it matches exactly the Microsoft's GDI+ implementation in DrawCurve() - this was achieved.

Function can be easily expanded to 3D.

While "Snap-to-Point" feature works quite well on femur, there are areas where local features are not sufficient to reliably detect the desired location

Problematic boundary for "Snap-to-Point"

Typical structure of the edges.  Local structure is not sufficient to reconstruct a good snapping location.

To solve this problem I propose to include additional mechanisms, see figure below.

"Snap-to-point" would simply snap to a stronger edge within the Snap apperture. This would be incorrect. Instead taking the previous state of the cardinal spline into account, we search for a better snap location.  Snap-to Curve would inregrate the edges strength all along the last segment, so the yellow path would be invalidated. And instead more reliable path chosen.

FireVoxel Build 210A is released.

Implemented the functionality to load real valued 4D Analyze files (*.time+ array of .IMG files)

First runs of new MagPoly tool on the femur:

First user performs several clicks on perceived contour of the femur. Computer calculates the edge pattern next to the click and selects a "snapping" location setting an anchor point.
Two important points:

a) Even if snapping did not work properly - operator proceeds with the next points (there will be a cleanup stage later).
b) Work is performed on a full Zoomout, so User does not have to Zoom In and back and scroll!
c) In between the anchor points, a cardinal spline with application-specific tension is used.
d) 10-voxel snapping radius was used.

Each anchor point corresponds to a single click

In the followup stage. User returns and drags some anchors to improve their positions. In this example about 6 anchors were corrected.

After dragging 6 anchors.

MagPoly tool: a simple interface to extend the functionality of the Polygon. It is purely 2D tool. No 3D extension is foreseen at the moment.



Tool is activated with the present Polygon tool. Then behavior changes according to dialog parameters.

|x|  UseMagPoly - turns the tool on.  Off = regular polyline.

"MagPoly radius":  the cursor changes to a semitransparent circle (similar to the paintbrush cursor). Radius specify the snapping seaarch radius - this way user has some feedback how far she should click.

|x|  Precompute slice edges (for slow computers).  - at the moment I plan to compute edges each time user clicks within the apperture specified by the "MagPoly radius".  Hopefully it will fill instantaneous on the mainstream computer.  Otherwise, with the tool on each time the slice would change, the internal edge layer will be computed.

"Edge Parameters" - parameters identical to the Texture Edge detector.


Additional parameters will appear later on.  F.e. more advance version would snap the curve between the user-specified Anchor points.

Implemented "ROI>Concentric Ring profile" function with the result being copied to the clipboard.

Idea is to capture the spatial characteristics of the tumor by detecting Texture-sensitive edges within the tumor at different scales and different apperture weights.

EMD texture edges, Scale=3, Apperture=constant

 Here are the corresponding Edge strength distribution histograms:  They have a widely varying StdDev/Mean and so on.

We can also Build the "Concentric Profiles" of Edge Strength distribution ( in corresponding order)

"Tumor blob analysis"

Tumor is thresholded.

Dark blob info is available

"Tumor ring profile" trials:

Mean=Blue, StdDev=red,  1 vox step -> inwards