simplify ProjDataInfoGeneric hierarchy#1696
simplify ProjDataInfoGeneric hierarchy#1696KrisThielemans wants to merge 9 commits intoUCL:masterfrom
Conversation
This is step 1 in UCL#1307 (comment) ProjDataInfoGeneric has no good reason to exist on its own, as it assumes discretised detectors already, as does ProjDataInfoGenericNoArcCorr. Merging the 2 simplifies the hierarchy.
40d60c0 to
a51fb74
Compare
|
Step 1 and 2 implemented. Warning: I will squash some commits here once it works. |
…Corr This is step 2 in UCL#1307 (comment) By deriving from ProjDataInfoCylindricalNoArcCorr, we can cut most functions in the Generic version, as they are duplicates.
d258b74 to
b9f8b61
Compare
removed one function as it's now implemented higher up (t is obsolete anyway)
|
Steps 1 & 2 are done, although I suddenly see segfaults in the MacOSDebug build in CI. I hope they will disappear with the later updates as that will be hard to debug (I have no access to a Mac). Note that step 3 is for v7, as at the moment the We could rename I think we only need 2 small changes to enable TOF (currently I still call |
The assertt() call was in the wrong place and caused recursive calls in the "generic" case. I took the opporttunity to remove on more dependency on boost.
|
@markus-jehl could you try this out, please? |
[ci skip]
also prepare for TOF (but still disabled)
We were using "delete", but that means they could be called inadvertently. This was now more confusing with the change in hierarchy. Instead, we now call error() in most cases. Also updated TOF functionality, but it's still disabled.
we currently ignore this field and rely on the detector map, so now check that it's zero.
4c711da to
787345c
Compare
|
The code is a bit safer now. (I started testing TOF and ran into some unexpected errors because of the "deleted" functions, so now we call |
|
Enabling a block scanner in Of course, this problem is identical to what is currently on |
|
@markus-jehl @NikEfth @danieldeidda I will merge this soon. It is working exactly as before, to the best of my knowledge. Do test, even after the merge... |
|
@KrisThielemans sorry, only saw this now. Managed to get around testing it now: works fine for me. |
This PR implements the steps discussed in #1307 (comment)