Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?

Hi Andreas, Done! I removed both python3-theano and python3-keras. Best regards. Em seg., 16 de jan. de 2023 às 09:54, Andreas Tille escreveu: > Hi Thiago, > > Am Sat, Jan 14, 2023 at 07:50:27PM -0300 schrieb Thiago Franco Moraes: > > Hi Rebecca, > > > > InVesal

Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?

Hi Rebecca, InVesalius can work without Theano (and Keras). It will use Pytorch. Best regards. Em sáb., 14 de jan. de 2023 às 08:12, Rebecca N. Palmer < rebecca_pal...@zoho.com> escreveu: > theano has been mostly abandoned upstream since 2018. (The Aesara fork > is not abandoned, but includes

Bug#927387: invesalius: crashes after splash screen

Hi David, I think I've found the problem. Devuan is using Python3.7 and InVesalius-bin was compiled using Python3.6. I tried to rename .so from *-36m*.so to *-37m*.so it work but with warnings. It's necessary to compile invesalius-bin to Python3.7. I don't know to proceed in this case. On Sun,

Bug#927387: invesalius: crashes after splash screen

Thanks for the bug report. What is the content of the folder /usr/lib/invesalius/invesalius_cy/ ? Em 18 de abr de 2019 17:03 -0300, David Paul escreveu: > Package: invesalius > Version: 3.1.2-2 > Severity: grave > > Dear Maintainer, > > When attempting to run InVesalius for the first time, I

Bug#901562: invesalius is marked for autoremoval from testing

Hi Andreas, Thanks, I can push to repository now. I've pushed both the master and upstream/3.1.1 Best regards On Sat, Aug 18, 2018 at 2:32 AM Andreas Tille wrote: > > Hi Thiago, > > On Fri, Aug 17, 2018 at 09:12:46PM -0300, Thiago Franco Moraes wrote: > > I' ve creat

Bug#901562: invesalius is marked for autoremoval from testing

. Best regards On Wed, Jul 11, 2018 at 12:35 PM Andreas Tille wrote: > > On Wed, Jul 11, 2018 at 12:18:28PM -0300, Thiago Franco Moraes wrote: > > > > I was thinking the second option. I'll create a new version tag, > > something like 3.1.9997, then I'll have a tarball wit

Bug#901562: invesalius is marked for autoremoval from testing

Hi Andreas, On Wed, Jul 11, 2018 at 3:30 AM Andreas Tille wrote: > > Hi Thiago, > > On Tue, Jul 10, 2018 at 09:39:12PM -0300, Thiago Franco Moraes wrote: > > I think the easiest way to fix this bug is to package the git version. > > Also, the git version is already worki

Bug#901562: invesalius is marked for autoremoval from testing

Hi Andreas, I think the easiest way to fix this bug is to package the git version. Also, the git version is already working with Python3. What do you think? Best regards. On Tue, Jul 10, 2018 at 3:27 AM Andreas Tille wrote: > > Hi Thiago, > > any news about this? Note that bug #901377 is fixed

Bug#901562: invesalius: Segmentation fault at startup

Hi Andreas, I reported the bug to the python-vtk6 package. Here the link https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902125 This bug will continue to open or do I have to do something to close it? Best regards, Thiago Franco de Moraes

Bug#902125: Segmentation fault at wxVTKRenderWindowInteractor

Package: python-vtk6 Version: 6.3.0+dfsg2-2+b2 When I run a python software that uses wxVTKRenderWindowInteractor a segmentation fault happens. This segmentation fault doesn't happen when the window manager is KDE. This segmentation fault happens when run in Gnome-shell and XFCE4. I haven' t

Bug#901562: invesalius: Segmentation fault at startup

b09 in ?? () > #88 0x5567b2be in ?? () > #89 0x5564e5d0 in PyEval_EvalFrameEx () > #90 0x5564e3e2 in PyEval_EvalFrameEx () > #91 0x5564e3e2 in PyEval_EvalFrameEx () > #92 0x55646c7a in PyEval_EvalCodeEx () > #93 0x55646709 in PyEval_E

Bug#901562: invesalius: Segmentation fault at startup

Hi, What window manager are your using? I don't why yet, but this error doesn't happen if you use KDE as window manager. It's happening also with the git version (https://github.com/invesalius/invesalius3). If you use the WXPython4 this doesn't happen, but you need to use the git version. Thanks

Bug#779655: invesalius: "ZeroDivisionError: float division by zero" upon importing DICOM X-ray videos

Thanks for your help, Andreas. On Fri, Sep 15, 2017 at 1:23 PM Andreas Tille <andr...@fam-tille.de> wrote: > On Fri, Sep 15, 2017 at 03:03:11PM +0000, Thiago Franco Moraes wrote: > > Andreas, yes, if it's possible. > > Done. Thank you for your contribution > > A

Bug#779655: invesalius: "ZeroDivisionError: float division by zero" upon importing DICOM X-ray videos

Andreas, yes, if it's possible. On Fri, Sep 15, 2017 at 12:00 PM Andreas Tille <andr...@fam-tille.de> wrote: > Hi Thiago, > > On Fri, Sep 15, 2017 at 01:52:37PM +, Thiago Franco Moraes wrote: > > I committed the patch to debian-med git repo of InVesalius.

Bug#779655: invesalius: "ZeroDivisionError: float division by zero" upon importing DICOM X-ray videos

I committed the patch to debian-med git repo of InVesalius. Also, I'll commit it to the upstream. On Fri, Sep 15, 2017 at 9:45 AM Thiago Franco Moraes <totonixs...@gmail.com> wrote: > Hi Andreas, > > I tested here the patch, it's not working with case it tries to fix. I'm >

Bug#779655: invesalius: "ZeroDivisionError: float division by zero" upon importing DICOM X-ray videos

Hi Andreas, I tested here the patch, it's not working with case it tries to fix. I'm hacking here a fix, it almost complete. I'll submit here the patch and I'll put it in the upstream. Thanks! On Fri, Sep 15, 2017 at 6:09 AM Andreas Tille wrote: > On Fri, Sep 15, 2017 at

Bug#779655: invesalius: ZeroDivisionError: float division by zero upon importing DICOM X-ray videos

Hi Andreas and Axel, We've not tested InVesalius with X-ray videos yet. Probably it does not work, because InVesalius is directed to work with CT, µCT and MRI. Your error must be because we make some assumptions about the dicom file which are not appropriate to x-ray videos. Axel, if possible,

Bug#779655: invesalius: ZeroDivisionError: float division by zero upon importing DICOM X-ray videos

Hi Axel, No, dicomdir is not enough. Well, I'll try to find on the internet some dicom samples. Thanks! On Wed, Mar 4, 2015 at 10:32 AM Axel Beckert a...@debian.org wrote: Hi Thiago, Thiago Franco Moraes wrote: We've not tested InVesalius with X-ray videos yet. Probably it does not work

Bug#759060: [o...@survex.com: Bug#759060: invesalius: Partial patch for wxPython 3.0]

/?page_id=8 On Sat, Sep 13, 2014 at 11:34 PM, Olly Betts o...@survex.com wrote: On Sat, Sep 13, 2014 at 02:10:42PM -0300, Olly Betts wrote: On Wed, Sep 10, 2014 at 04:25:23PM -0300, Thiago Franco Moraes wrote: I don't know if it's my setup here. But I think there is a problem in the interaction

Bug#759060: [o...@survex.com: Bug#759060: invesalius: Partial patch for wxPython 3.0]

created a branch to port invesalius to wxPython3. Best regards! [1] - https://groups.google.com/forum/#!topic/wxpython-users/MxJPxlOS05A On Wed, Sep 10, 2014 at 9:52 AM, Thiago Franco Moraes tfmor...@cti.gov.br wrote: Hi Andreas, Thanks for notify me about this patch. I was a little off, so I

Bug#759060: [o...@survex.com: Bug#759060: invesalius: Partial patch for wxPython 3.0]

Hi Andreas, Thanks for notify me about this patch. I was a little off, so I haven't seen it. I have a branch of invesalius which works with wxpython3, at least in MacOSX. I'm going to test it in Debian and see if it works, and if works I'll generate a patch and create new debian package with this

Bug#746708: missing license in debian/copyright

Hi Andreas, On Mon, May 12, 2014 at 5:05 PM, Andreas Tille andr...@an3as.eu wrote: Hi Thiago, On Mon, May 12, 2014 at 04:39:31PM -0300, Thiago Franco Moraes wrote: Fixed with the help of cme and this link [1]. It was a problem with the license short name and a grammar error. I think it's

Bug#746708: missing license in debian/copyright

, Thiago Franco Moraes wrote: Hi Andreas, Sorry! I was out for some time. I added the copyright info about invesalius\gui\widgets\platebtn.py. I don't know if its correct, since I'm getting a lintian warning about the license name (field-name-typo-in-dep5-copyright licence). Thanks

Bug#708258: pyversions: missing X(S)-Python-Version in control file

Hi Mathie, I followed the link you indicated [1] and I've made the transition to dh_python2 (remove d/pyversion, provide X-Python-Version, etc). It seems to be right now. The changes are available on debian-med svn. Thanks! [1] - http://wiki.debian.org/Python/TransitionToDHPython2 -- To

Bug#708259: Depends: is hardcoded

I removed libvtk and libgdcm as dependencies to InVesalius. Now, it's depending on python-vtk, python-vtkgdcm and python-gdcm, which are the python bindings to vtk and gdcm. The changes are on debian-med svn. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject

Bug#708260: ImportError: cannot import name setuparg1

I'm not sure about how to proceed in this case. When we updated wxPython from 2.8.10 to the last version, we had to rewrite some codes. To support wxPython 2.8.10 I'd have to write some patches, and it wouldn't be compatible with the last wxPython version. Maybe, the best thing to do is set the

Bug#693963: ITP: python-casmoothing -- Context-aware mesh smoothing for biomedical applications

Package: wnpp Owner: Thiago Franco de Moraes tfmor...@cti.gov.br X-Debbugs-CC: debian-...@lists.debian.org Severity: wishlist * Package name: python-casmoothing Version : 0.1.0 Upstream Author : Thiago Franco de Moraes tfmor...@cti.gov.br * URL :

Bug#575873: ITP: sigar -- A cross-platform API for collecting software inventory data

Package: wnpp Severity: wishlist It can be downloaded by svn checkout from trunk, the last stable version doesn't compile: svn co http://svn.hyperic.org/projects/sigar_mirror/trunk sigar Here is the site http://www.hyperic.com/products/sigar Packages I created: