Konstantinos Ntatsis

@mstaring @N-Dekker Is the issue resolved for elastix 4.9? Because I am using elastix 5.0 as static library and it seems not to be thread-safe. I have tried both the...

It seems that there are two (at least) groups of things that are making elastix not thread safe. After certain modifications in the current develop branch, I was able to...

Thanks for the reply, @N-Dekker! Yes, in the naive option that I followed each `ElastixMain` object has its own `ComponentDatabase` with exactly the same content. However, even in the application...

@N-Dekker, from a quick search in the elastix codebase I see that `ElastixMain::GetComponentDatabase()` (as well as its Set counterpart) are called limited times and always through an `ElastixMain` object. So,...

@stefanklein Great flashback from the elastix past indeed! ;) @N-Dekker Sorry, I was not explicit. I was mainly worried about the `ElastixMain::UnloadComponents`: https://github.com/SuperElastix/elastix/blob/3acd58e5efbe820305f4ba696bdaab4658a39861/Core/Kernel/elxElastixMain.cxx#L760-L776 But I think that this is a...

Hi @N-Dekker, thank you for your work so far on this issue and now continuing with the logger! I have started looking at the implementation details of the current logger...

@N-Dekker Indeed, that would be useful. We only use the transformation parameter values internally in the code and we don't output anything to file/console (`LogToConsoleOff()` & `LogToFileOff()`).

Hi @N-Dekker, I did a quick test with the branch using `ELASTIX_USE_OPENMP = OFF` and it passes the gtests. However, when I run my code I get in the console...

I made a pull request that seems to work: https://github.com/SuperElastix/elastix/pull/406. I tested it on my application and it runs with no issues but I haven't tried the gtests. Bonus: it...

Hi @N-Dekker, that could be an option. However, I also see that currently, _all_ the `#pragma omp`s of the main code (11 in total) are deactivated by forcing either ITK...