Developer's notes

Current (priority)

visualisation of voxelized volume with 3D slices
materials issue #282
Refactor sources
Refactor actors
Dose actor revisited:
- MT with lock (array of lock?), ~~or semaphore?~~(checked: not good for protecting shared resources) or one dose map per thread (+merge)? NK: I would look into the « combinable » class from the TBB library. Seems quite spot on for us.
- inheritance: DoseActor LETActor FluenceActor etc
Notes on MT/images:
- https://stackoverflow.com/questions/32634995/how-can-i-lock-a-mutex-for-an-element-in-the-array-not-for-the-complete-array
- https://stackoverflow.com/questions/34519/what-is-a-semaphore
Update MT with windows(wait PR json)
~~Consolidate: Simulation user API and rename geometry_manager~~
Retrieving repeated volumes of detailed information (position etc), once built. Important for PET design
~~Consolidate subprocess system: handle subprocessing in Simulation class (rather than engine)~~
Material manager: unified way to create/read/define materials
~~dynamic~~ #319

remove unnecessary warning in RepeatParametrisedVolume (issue #279)
in ImageVolume: dump also sorted LUT if a label image is requested so the user can associate labels and materials.
option in ImageVolume to assign origin and rotation in an inout image as translation and rotation to the ImageVolume object
Check and improve RepeatParametrisedVolume
The repeat_ring helper function is somewhat unintuitive, in particular the translation parameter which is applied to the first repetition. Would it not be more intuitive to define the ring's center and the distance to the rotation axis?
The "translation" parameter in the context of repeated volumes should be renamed because it interferes with the common parameter "translation" of volumes. Something like "spacing" would be better I think. REPETITION GROUP
Similarly, the "offset" and "offset_nb" parameters are strange. In my understanding, this is more like a nested repetition, or block repetition. In that case, the name might be revisited. To be checked.
SolidBase.get_solid_info() should better be a property rather than a method
Fix wrong wiggly lines under attributes in pyCharm