Alena Ulla Uus

Hi Andreas, Thank you for your reply. As far as I remember it was a linker error and I managed to fix it - but 'scalable_allocation_command' does not work in...

Yes, using tbb::memory_pool would be the optimal solution (I tested it separately on a simple code and it resolves the issue). But in reality I am simply not sure how...

As far as I remember I tried using memory_pool_allocator for 'RealImage' but eventually gave up. Will try it again. It seems that the issue originates in the logic of implementation...

Thanks for the suggestion it really makes sense to pre-instantiate objects. I've sent you the code and a dataset example to @imperial email. p.s we have the same memory issue...

hello yes for some reason the new MIRTK TBB "fix" led to significantly slower performance .. i had to revert it back i would suggest using the svrtk docker open...

It looks like some of the slices were excluded .. Could you please run it with "-no_robust_statistics " option?

The error was related to the name of the output file .. In you case, you might also decrease the number of iterations to 1 or 2 I to make...

Very strange indeed! Are you sure that you used "-no_robust_statistics" option. If it is ok - could you please send me the dataset and I will check what is wrong?...

we use both TBB (parallelisation of the main computational components ) and openmp for historical reasons and there are no options to set the number of cores yes unfortunately i...

hello, SVRTK reconstruct method was designed for fetal MRI and expects more than 3 stacks with different orientations for reconstruction. i.e., the ROI should be sufficiently oversampled and reconstruction from...