Hi Peter,

Hope you all at DKFZ are doing well.
Sorry for reviving this old email thread. We had kind of pushed this down
the priority list back then.

Does this creation of python plugins/modules using python 3 work with MITK
version 2018.04.2 or do we need the latest MITK sources  for this?

Thanks,
Ashish

On Tue, Jan 7, 2020 at 2:57 AM Neher, Peter <p.ne...@dkfz-heidelberg.de>
wrote:

> Dear Ashish,
>
>
> sorry for the late reply. You can find examples for views doing what you
> would like to achieve here:
>
>
> https://github.com/MIC-DKFZ/MITK-Diffusion/tree/master/Plugins/org.mitk.gui.qt.diffusionimaging.python/src/internal
>
>
> Only works with python 3.
>
>
> Best,
>
> Peter
>
>
>
> ---------------------------------------------------------------------------------------------------
>
> *Dr. Peter F. Neher*
>
> Division of Medical Image Computing
>
> Scientist & Division Board Member
>
>
>
> German Cancer Research Center (DKFZ)
>
> Foundation under Public Law
>
> Im Neuenheimer Feld 280
>
> 69120 Heidelberg
>
> Germany
>
> phone: +49 6221 42-2330
>
> fax:      +49 6221 42-2345
>
>
>
> p.ne...@dkfz.de
>
> www.dkfz.de
>
>
>
>
>
> Management Board: Prof. Dr. Michael Baumann, Prof. Dr. Josef Puchta
>
> VAT-ID No.: DE143293537
> ------------------------------
> *Von:* Ashish Singh <asinghmli...@gmail.com>
> *Gesendet:* Donnerstag, 12. Dezember 2019 19:32
> *An:* Dinkelacker, Stefan
> *Cc:* mitk-users@lists.sourceforge.net
> *Betreff:* Re: [mitk-users] Python
>
> Hi Stefan,
>
> We are using MITK version 2018.04.02 and creating our own plugins. We now
> need to invoke python scripts that requires some python packages(such as
> scikit-learn, numpy, pandas, etc.) and we want it to be callable from our
> plugins and also obviously pass it images or CSVs as input and somehow get
> the files produced by the script in our C++ code.  We are also Ok with
> using Python 2 for now.
>
>
>
> Is there any example for this that we can take a look at?
>
>
> Thanks,
>
> Ashish
>
>
> On Thu, Nov 21, 2019 at 3:25 AM Dinkelacker, Stefan <
> s.dinkelac...@dkfz-heidelberg.de> wrote:
>
>> Hi,
>>
>>
>>
>> I am not using Python with MITK but a few months ago I improved MITK’s
>> Python 3 integration as it was a little chaotic before and was a pain to
>> set up in CI. It was only merged into our master branch though, as our
>> CMake interface changed a little (it’s MITK_USE_Python3 now compared to the
>> old MITK_USE_Python). More information here [1].
>>
>>
>>
>> Python 3.6 Is just fine, but since October Python 3.7 is supposed to work
>> as well [2].
>>
>>
>>
>> If you’re working with macOS, see the comment in T26559 related to
>> CMAKE_FRAMEWORK_PATH if you have issues setting a specific Python
>> installation.
>>
>>
>>
>> [1] https://phabricator.mitk.org/T26559
>>
>> [2] https://phabricator.mitk.org/T26701
>>
>>
>>
>>
>>
>> *From:* Dimitris Bounias [mailto:bounias.dimit...@gmail.com]
>> *Sent:* Wednesday, November 20, 2019 7:58 PM
>> *To:* mitk-users@lists.sourceforge.net
>> *Subject:* [mitk-users] Python
>>
>>
>>
>> Greetings,
>>
>>
>>
>> We want to build mitk and develop plugins and some of those plugins will
>> use python. We prefer python 3.6.
>>
>>
>>
>> 1) Is there any way to use python 3.6 on MITK 2018.04.2? Or is that a
>> feature of an upcoming release? If yes, is there a rough timeline for the
>> next release?
>>
>>
>>
>> 2) We can't build with python 2.7 either. But maybe that's a problem from
>> our side. We specified MITK_USE_PYTHON, PYTHON_EXECUTABLE,
>> PYTHON_INCLUDE_DIR, PYTHON_LIBRARY to our distribution's default paths, but
>> the build was complaining about "bad install directory or PYTHONPATH". This
>> is under linux mint 19.2 (basically ubuntu 18.04)
>>
>>
>>
>> Thanks a lot!
>>
>> Dimitris
>> _______________________________________________
>> mitk-users mailing list
>> mitk-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mitk-users
>>
>
_______________________________________________
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to