Skip to content

Commit 6eb7c15

Browse files
authored
Merge pull request #129 from loli/HOTFIXES_release
Hotfixes release
2 parents 91b288c + 4b83d7a commit 6eb7c15

File tree

3 files changed

+40
-8
lines changed

3 files changed

+40
-8
lines changed

CHANGES.txt

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,9 @@
1+
v0.5.0, 2024-04-XX -- Addressed all depreciation warnings and incompatabilities
2+
Updated documentation
3+
Updated and fixed tests
4+
Added github workflows as system
5+
Introduced formatting rules and pre-commit to enforce them
6+
Removed dockerfile creation files
17
v0.4.0, 2018-02-XX -- Switched to Python 3: finally compatible with modern development environements
28
Switched to simple itk for image loading/saving: read dicom series, more formats, less dependencies, cleaner code, easier to maintain
39
Documentation: installation instructions for Windows and OsX

doc/source/installation/conda.rst

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,10 @@
22
Installing MedPy with Conda
33
===========================
44

5-
**MedPy** does not come with an official conda package.
6-
But you can nevertheless install it into a conda environement using *pip* after resolving the dependencies.
5+
**MedPy** can be installed from `conda forge <https://anaconda.org/conda-forge/medpy>`:
76

87
.. code-block:: bash
98
10-
conda install -c simpleitk simpleitk
11-
python3 -m pip install medpy
9+
conda install conda-forge::medpy
1210
13-
Note that the graph-cut package won't compile in the conda environement due to unmet dependencies.
14-
15-
For conda-purists: The friendly folks from `bioconda <https://bioconda.github.io/>`_ wrapped the previous (0.3.0) version of **MedPy**
16-
into their distribution system (see https://anaconda.org/bioconda/medpy).
11+
Note that the graph-cut package might not compile in the conda environement due to unmet dependencies.

doc/source/installation/graphcutsupport.rst

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,3 +18,34 @@ These dependencies can be found in the repositories of all major distribution. F
1818
sudo apt-get install libboost-python-dev build-essential
1919
2020
Then install **MedPy** the usual way.
21+
22+
Troubleshooting
23+
---------------
24+
25+
If you experience an error like `ModuleNotFoundError: No module named 'medpy.graphcut.maxflow'`, this usually means
26+
that the `graphcut`` module has not been compiled successfully. To check the error log, try re-installing **MedPy** with:
27+
28+
.. code-block:: bash
29+
30+
pip install medpy --no-cache-dir --force-reinstall -v
31+
32+
In the logs, you might see the following warning:
33+
34+
.. code-block:: bash
35+
36+
2021-06-30T11:07:32,684 ***************************************************************************
37+
2021-06-30T11:07:32,685 WARNING: The medpy.graphcut.maxflow external C++ package could not be compiled, all graphcut functionality will be disabled. You might be missing Boost.Python or some build essentials like g++.
38+
2021-06-30T11:07:32,685 Failure information, if any, is above.
39+
2021-06-30T11:07:32,685 I'm retrying the build without the graphcut C++ module now.
40+
2021-06-30T11:07:32,685 ***************************************************************************
41+
42+
The error should be detailed in the lines just above.
43+
44+
Usually, it is a problem with the linking of the `(lib)boost_python3`` lib.
45+
There are some inconsistent naming conventions around, rendering the file undiscoverable to **MedPy**.
46+
47+
On Ubuntu, you should be able to locate your *libboost_python3x.so* under `/usr/lib/x86_64-linux-gnu/`.
48+
If your shared library file is named differently than **MedPy** expects, you might have to create a softlink like, e.g.:
49+
50+
.. code-block:: bash
51+
sudo ln -s libboost_python38.so libboost_python3.so

0 commit comments

Comments
 (0)