btrack icon indicating copy to clipboard operation
btrack copied to clipboard

Import Error for Mac M1

Open samueljrosen opened this issue 1 year ago • 1 comments

Dear All, I have been working with the example notebook for btrack and have been running into numerous problems with visualizing my final result. I either encounter one of two errors:

The first error is when I follow the installation for MacOS listed on the GitHub. I am able to successfully install napari and btrack, however I encounter errors when trying to launch the GUI. The code run smoothly until the napari viewer portion, in which I get the following:

Screen Shot 2022-07-26 at 3 49 48 PM

When I try to install QtPy5 into the environment, I get the following error:

Screen Shot 2022-07-26 at 3 53 46 PM

I am including my environment for this error, titled btrack_env.yml, such that you can replicate my error.

Next, I tried to set up the dependencies myself by going through the environment folder and pip/conda installing the packages. I started with installing Python=3.8.13, QtPy, Napari and btrack and had success. When I went to install pyqt5, I once again ran into an installation error, which prevents me from using the gui. I get an output like the one below:

Screen Shot 2022-07-26 at 2 52 32 PM

I am including this environment in my zip file with the name testing.yml so you can replicate my error.

Any insight or help with instillations would be much appreciated. Conda_Env.zip

samueljrosen avatar Jul 26 '22 21:07 samueljrosen

Hi @samueljrosen,

Yes, it can be a bit tricky on M1. I've found the following to work:

  • Start a clean conda environment
  • Install napari first, using their guidelines
  • Then conda install -c conda-forge cvxopt h5py
  • Then pip install btrack

Let me know if you still have issues.

quantumjot avatar Aug 12 '22 14:08 quantumjot

This is blocked by cvxopt/cvxopt#234. I'm having the same issue...

paddyroddy avatar Mar 20 '23 23:03 paddyroddy

@samueljrosen can you try running conda install -c conda-forge cvxopt and trying again?

paddyroddy avatar Apr 25 '23 16:04 paddyroddy

This will be fixed/documented in #306.

paddyroddy avatar Apr 26 '23 10:04 paddyroddy