-
Notifications
You must be signed in to change notification settings - Fork 29
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
Error raised in AcquisitionSensitivityModel.[un]normalise methods applied to a read-only object #1299
base: master
Are you sure you want to change the base?
Conversation
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.
I'm a bit confused about the catching of a STIR error. As you saw, python just exited due to uncaught exception presumably. I'm not sure what try_calling
does, but it looks like it didn't catch it.
Calling STIR functions could always get into stir.error
, so I think it'd be safest to make sure we catch that somehow. Easy?
So far as I can see, methods |
Build error:
|
The build error is due to gadgetron/gadgetron#1277. They haven't looked at my PR yet. I've downgraded to GHA to use Ubuntu 22.04 in #1302, so merging |
I don't know what's going on there, but as mentioned in #1298 (comment), STIR does throw an exception (see the error |
The modifications to use the |
Changes in this pull request
Error raised in
AcquisitionSensitivityModel.[un]normalise
methods if applied to a read-only object.Testing performed
Yes
Related issues
fixes #1298
Checklist before requesting a review
Contribution Notes
Please read and adhere to the contribution guidelines.
Please tick the following: