-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
block and generic scanner geometry #577
Conversation
list of modified classes: - InterfileHeader - interfile.cxx - Scanner - VoxelsOnCartesianGrid - LORCoordinates - CListRecordSAFIR - DataSymmetriesForBins_PET_CartesianGrid - ProjMatrixByBinUsingRayTracing list of added classes: - GeometryBlocksOnCylindrical - ProjDataInfoBlocksOnCylindrical - ProjDataInfoBlocksOnCylindricalNoArcCorr
https://travis-ci.org/github/UCL/STIR/jobs/697593231#L3130-3142 says
Not sure why all the previous |
same problem when compiler
|
- moved some inline functions to .cxx. They were either not used frequently or probably too big to be inlined - made some member functions const and pass "bigger" arguments as references - avoid some warnings about double->float conversion The first item resolves a problem with SWIG compilation UCL#604 by working around it.
They aren't used, and probably more confusing than anything else.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pkhateri I've resolved the SWIG compilation error. However, there are now a lot of failures in the tests. Many of them just state
ERROR: Crystal Map not defined!
Python tests show
RuntimeError: ProjDataInfoGeneric::get_ring_pair_for_segment_axial_pos_num does not work for data with axial compression
implying that ProjDataInfoGeneric
is called for "normal" interfile headers.
I do not understand your intentions with this PR well enough to solve this. Can you help?
@@ -42,7 +44,7 @@ | |||
#include "boost/cstdint.hpp" | |||
|
|||
#include "stir/listmode/DetectorCoordinateMapFromFile.h" | |||
|
|||
#include "boost/make_shared.hpp" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not needed. You can use either MAKE_SHARED
(or even std::make_shared
now that we're C++11).
Example Travis test log https://travis-ci.org/github/UCL/STIR/jobs/707731577 |
…when the scanner geometry is not defined in the header
I pushed some fixes to the repository. Now all the tests should pass. |
thanks @pkhateri sorry for the delay. Thanks for the extra utilities. Could you add some brief info on them in the STIR_UsersGuide.tex? Ideally also a bit more documentation in their headers (doxygen) if it isn't immediately obvious what they do. I'm reluctant to add the following though:
Please also update |
created text for voxel on cartesian grid
as opposed -VV, we only output failed tests now, preventing log overrun [actions skip]
@danieldeidda Appveyor builds are all failing on It runs fine on my Visual Studio, so I suspect this it hits a memory limit, as these tests use ~6GB. I think best to use |
I think we can remove the following: as the symmetry_z is also disabled |
I guess we cannot remove it, but have to rephrase it to "all symmetries disabled". However, I was talking about compilation warnings (as you can see in the Appveyor log). The MS VC compiler issues far more warnings than gcc... |
the all seem to be conversion from 'double' to 'float' Anyway do you want the scatter changes to be pushed here or we merge to master first? |
yup. needs some (ugly)
I'd like to merge this to master first. |
This should be my last commit for this PR I guess |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks. A few more unfortunately. sorry
Co-authored-by: Kris Thielemans <KrisThielemans@users.noreply.github.com>
Co-authored-by: Kris Thielemans <KrisThielemans@users.noreply.github.com>
can you fix white-spacing any the
|
OK I think I have done all the corrections |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
more things to do, but we'll merge this now as it's in good shape.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry. hit the wrong button!
@pkhateri This is merged now. Thanks a lot! I've sent an email to the list, but don't seem to have an email address for you anymore. I hope that this messages reaches you. All the best. |
new classes and changes for accurate scanner geometry