- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 17 2017
Oct 19 2016
Oct 18 2016
Oct 17 2016
A better solution to this issue is provided by the MatchPoint-UIs which were recently merged into master ( T20000 )
Oct 11 2016
Sep 30 2016
Pushed new branch T19993-PVAnalysis-MaskHandling.
It is not the casting between different types, it is rather showing random memory content, so it is likely that the memory used in the mask image is somehow freed by the original holder.
Sep 16 2016
Pushed new branch T19986-Crash_BasicImageProc_Resampling.
Sep 4 2016
Pushed new branch T19924-MLTraining-CrashOnLargeDatasets-debugging.
Sep 2 2016
The filter is already there, any further extension of it should be documented within T15884
not working on this currently...
The issue is meanwhile invalid, after re-factoring the Reader/Writer to a Service.
Pushed new branch T19924-MLTraining-CrashOnLargeDatasets.
ad 2. There is no obvious source of possible memory-access-errors, the filter runs successfully with lower number of tracts ( 120k ). Trying to figure out possible reasons with a valgrind-memcheck run (on a smaller test-problem).
The filter was moved within the rMITK00c39be56 commit. Closing task.