Closed surajpaib closed 2 months ago
@alexzwanenburg It would be very useful for bug reporters to check the version of MIRP with a call like
mirp.__version__
@alexzwanenburg It would be very useful for bug reporters to check the version of MIRP with a call like
mirp.__version__
The use of __version__
was never accepted in a PEP. Notably, PEP 396 was formally rejected. The pythonic way to get the installed version of MIRP is:
import importlib_metadata
importlib_metadata.version("mirp")
I will add instructions to the bug report template.
Expected behaviour
If
slice_id
is beyond number of slices, throw an error or a warning and use the maximum slice numberObserved behaviour
MIRP uses the middle slice instead when passed any value beyond the max. slice number
What did MIRP actually do? What error (if any) was produced?
Steps to reproduce the problem
The above displays slice 26 on the visual panel
Specifications