93 replies to this topic

[Rolf]

Hi,

 

The "epic thread" New stacking software project "PlanetarySystemStacker" has been going on for about two years now. Many of you actively contributed to the discussion which was a big help in the process to make the software mature and useful for many application scenarios. I thank you all very much for your dedication and patience!

 

Now it is time to organize the discussion in a better way. I suggest that we split it in two threads. This one will be the place where we discuss installation issues on the various hardware platforms and OS versions. Since PSS can be used on almost any computing platform, many special cases have to be dealt with. Often users encounter issues which do not show on the limited set of platforms where I do my tests. In the past experienced users gave valuable advice to others who reported problems which they had resolved already.

 

I will start another thread where we discuss program features, "best practices" in using PSS, and user experiences with the program.

 

I hope that you will find this new organization useful, and that we don't loose contact in this transition. I'm very much looking forward to the continued exchange with you on PSS in this new setting.

 

All the best,

 Rolf

Edited by Rolf, 29 January 2021 - 04:49 AM.

[daniele.bonfiglio]

Dear Rolf,

up to now I have always installed PSS on my Windows 10 pc using the windows installer.

Today I have succesfully installed Python (version 3.6.8 as recommended in the PSS user guide) and then PSS 0.8.31 via pip.

Just a quick question: do you suggest to upgrade pip?

Indeed, doing "pip3 install planetary-system-stacker", after the succesful installation of PSS, I get this message:

 

You are using pip version 18.1, however version 21.0.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.

 

Thank you and best regards, Daniele

[Rolf]

Dear Daniele,

 

If the installation was successful, you can just ignore the message to update pip. Can you start the PSS program successfully?

 

All the best,

 Rolf

[daniele.bonfiglio]

Dear Rolf,

thanks. Yes, the PSS installation was successful and I can start PSS without any problem. So I will keep this version of pip.

By the way, another minor question: when installing PSS with pip, is the PSS documentation installed as well? I cannot find it in the installation folder Python\Python36\Lib\site-packages\planetary_system_stacker

Best, Daniele

[Rolf]

Dear Daniele,

 

No, the documentation is not available from the PyPI server. But you can always download the current handbook from Github.

 

All the best,

 Rolf

[gordoabc]

I am unable to upgrade beyond 0.8.15 on macos, I think this is due to having python 3.9.5.  It trys to upgrade to 0.8.16 and 0.8.17 but both fail when trying to install numpy 1.18.4 (this may be the python 3.9 issue).  I have numpy 1.21.0 installed via homebrew. 

 

I tried manually installing pss 0.8.31.3 via whl and had the same issue.  Is it possible to ignore numpy 1.18.4 dependency and proceed or do I have to drop back to python 3.8?

 

later addition: simple fix in .zshrc:

 

alias python3.8="/usr/local/Cellar/python@3.8/3.8.10/bin/python3"
alias pss-upgrade="python3.8 -m pip install --upgrade planetary-system-stacker"

Edited by gordoabc, 27 June 2021 - 10:40 PM.

[DeepSky Di]

I am unable to upgrade beyond 0.8.15 on macos, I think this is due to having python 3.9.5.  It trys to upgrade to 0.8.16 and 0.8.17 but both fail when trying to install numpy 1.18.4 (this may be the python 3.9 issue).  I have numpy 1.21.0 installed via homebrew. 

 

I tried manually installing pss 0.8.31.3 via whl and had the same issue.  Is it possible to ignore numpy 1.18.4 dependency and proceed or do I have to drop back to python 3.8?

 

later addition: simple fix in .zshrc:

 

alias python3.8="/usr/local/Cellar/python@3.8/3.8.10/bin/python3"
alias pss-upgrade="python3.8 -m pip install --upgrade planetary-system-stacker"

I'm running macOS Big Sur 11.5.2 and want to run Planetary System Stacker.

So far I have installed homebrew, installed Python 3.9.7, managed to get it to be the default python, installed PSS successfully. When I run PSS from the terminal, I get an error

  ModuleNotFoundError: No module named 'numpy.random.bit_generator'

Due to this post, I'm assuming I have to downgrade to 3.8.10 using Homebrew.

[seymorejenkins]

I am running macOS Big Sure 11.6 and had the same issue when trying to run PSS. I have python 3.9.6 and have the error:

    ModuleNotFoundError: No module named 'numpy.random.bit_generator'

 

Did you end up figuring out a solution to this problem? I am fairly new at coding and using PSS, so I would appreciate any input! 

[DeepSky Di]

I am running macOS Big Sure 11.6 and had the same issue when trying to run PSS. I have python 3.9.6 and have the error:

    ModuleNotFoundError: No module named 'numpy.random.bit_generator'

 

Did you end up figuring out a solution to this problem? I am fairly new at coding and using PSS, so I would appreciate any input! 

Here's how I told it to the Mac user thread: 

 

Just for everyone's entertainment here's the wrong thing to do:

- go ahead and install the latest and greatest python 3.9.7 from python.org. If you ever manage to get it to be the default and run instead of python 2.7, you will find that PSS can't use it. There's a "numpy" file whose name got changed by its devs to begin with an extra _, breaking a lot of Python code that uses it, including PSS.

- install homebrew to install python 3.8 - well, the python 3.9.7 is still lurking there and will be the default

- use homebrew to unintall 3.9.7 - nope, it can't uninstall what it didn't install

- install pyenv to manage the python installs and specify the one you want to use. Too late, 3.9.7 is there already and no matter what you do with pyenv, 3.9.7  will take precedence.

- Google "how to uninstall python 3.9" - a lot of replies saying don't do that, just manage it with homebrew and / or pyenv.

I wasn't aiming for a master's degree in unix and python here, just trying to denoise my planetary photos on Mac without caving and using Windows.

 

=================

 

I spent most of Sunday wrestling with this, could not get the right python installed in the right place. Also an "alias" command that went wrong means that "python" actually does nothing, doesn't start 2.7 which is still there. 

 

It's going to be the weekend before I can get back to this. I'll report back if I get it working.

 

For the PSS team - please tell people the recommended version of Python to use, and recognize that not everyone is a pythonista.

[seymorejenkins]

Thanks for all the feedback! That is helpful and good to know. 

 

So I am not sure exactly what I did, perhaps python 3.9.6 was not my default, but I went to https://www.python.o...ase/python-380/ and installed python 3.8. I then reinstalled planetarysystemstacker through python 3.8, and it seems to work so far. For the first time, I got the GUI to open. 

 

checking in terminal with python3 --version it now says my version is 3.8

 

Hopefully that helps! Also, please let me know if what I did was improper or has any negative consequences. I've only started using python3 recently for the sole purpose of trying to run PSS, but will eventually be learning how to use it more. 

[DeepSky Di]

I got PSS working after deleting Python 3.9.7 and aliasing "python" to "python3" which is now 3.8.12, installed via Homebrew. I will leave pyenv until such time as I ever need mulitple python versions running.

 

First impressions, it seems very simple to get to work, and I really like the "go back" menu. 

 

Thank you Rolf for making this available cross platform. 

[Tailspin45]

Eager to make PSS work on Mac with OS 11.6 (Big Sur), but I have zero Unix and Python knowledge or experience.

 

However, by cook-booking the process using the PSS manual (yes, I did RTFM) I installed Python which appears to be version 3.10.0 date Oct 4, 2021

 

When I executed

pip3 install planetary-system-stacker

a bazillion versions of matplotlib were downloaded, but it terminates with these messages

Collecting planetary-system-stacker
  Using cached planetary_system_stacker-0.8.16-py3-none-macosx_10_6_intel.whl (227 kB)
  Using cached planetary_system_stacker-0.8.15-py3-none-macosx_10_6_intel.whl (214 kB)
  Using cached planetary_system_stacker-0.8.14-py3-none-macosx_10_6_intel.whl (209 kB)
  Using cached planetary_system_stacker-0.8.13-py3-none-macosx_10_6_intel.whl (208 kB)
  Using cached planetary_system_stacker-0.8.12-py3-none-macosx_10_6_intel.whl (208 kB)
  Using cached planetary_system_stacker-0.8.11-py3-none-macosx_10_6_intel.whl (208 kB)
  Using cached planetary_system_stacker-0.8.10-py3-none-macosx_10_6_intel.whl (208 kB)
  Using cached planetary_system_stacker-0.8.9-py3-none-macosx_10_6_intel.whl (208 kB)
  Using cached planetary_system_stacker-0.8.8-py3-none-macosx_10_6_intel.whl (208 kB)
  Using cached planetary_system_stacker-0.8.7-py3-none-macosx_10_6_intel.whl (207 kB)
  Using cached planetary_system_stacker-0.8.6-py3-none-macosx_10_6_intel.whl (207 kB)
  Using cached planetary_system_stacker-0.8.5-py3-none-macosx_10_6_intel.whl (206 kB)
  Using cached planetary_system_stacker-0.8.4-py3-none-macosx_10_6_intel.whl (205 kB)
  Using cached planetary_system_stacker-0.8.3-py3-none-macosx_10_6_intel.whl (204 kB)
  Using cached planetary_system_stacker-0.8.2-py3-none-macosx_10_6_intel.whl (204 kB)
  Using cached planetary_system_stacker-0.8.1-py3-none-macosx_10_6_intel.whl (204 kB)
  Using cached planetary_system_stacker-0.8.0-py3-none-macosx_10_6_intel.whl (204 kB)
ERROR: Cannot install planetary-system-stacker==0.8.0, planetary-system-stacker==0.8.1, planetary-system-stacker==0.8.10, planetary-system-stacker==0.8.11, planetary-system-stacker==0.8.12, planetary-system-stacker==0.8.13, planetary-system-stacker==0.8.14, planetary-system-stacker==0.8.15, planetary-system-stacker==0.8.16, planetary-system-stacker==0.8.17, planetary-system-stacker==0.8.2, planetary-system-stacker==0.8.3, planetary-system-stacker==0.8.4, planetary-system-stacker==0.8.5, planetary-system-stacker==0.8.6, planetary-system-stacker==0.8.7, planetary-system-stacker==0.8.8 and planetary-system-stacker==0.8.9 because these package versions have conflicting dependencies.

The conflict is caused by:
    planetary-system-stacker 0.8.17 depends on matplotlib
    planetary-system-stacker 0.8.16 depends on matplotlib
    planetary-system-stacker 0.8.15 depends on matplotlib
    planetary-system-stacker 0.8.14 depends on matplotlib
    planetary-system-stacker 0.8.13 depends on matplotlib
    planetary-system-stacker 0.8.12 depends on matplotlib
    planetary-system-stacker 0.8.11 depends on matplotlib
    planetary-system-stacker 0.8.10 depends on matplotlib
    planetary-system-stacker 0.8.9 depends on matplotlib
    planetary-system-stacker 0.8.8 depends on matplotlib
    planetary-system-stacker 0.8.7 depends on matplotlib
    planetary-system-stacker 0.8.6 depends on matplotlib
    planetary-system-stacker 0.8.5 depends on matplotlib
    planetary-system-stacker 0.8.4 depends on matplotlib
    planetary-system-stacker 0.8.3 depends on matplotlib
    planetary-system-stacker 0.8.2 depends on matplotlib
    planetary-system-stacker 0.8.1 depends on matplotlib
    planetary-system-stacker 0.8.0 depends on matplotlib

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies
WARNING: You are using pip version 21.2.3; however, version 21.3 is available.
You should consider upgrading via the '/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10 -m pip install --upgrade pip' command.

I have no clue how to fix the problem.

 

Can someone lead me by the hand?

Edited by Tailspin45, 20 October 2021 - 11:25 AM.

[theritz]

@Tailspin45: it tells you to upgrade pip to version 2.3 using the command (see the last line) /Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10 -m pip install --upgrade pip

 

After you do that run the pip3 install planetary-system-stacker command again.

[theritz]

Then my own problem (and of a fellow amateur astronomer with an M1 Mac). 

If I install using

pip3 install planetary-system-stacker

 

I get this error

 

ERROR: Could not find a version that satisfies the requirement planetary-system-stacker (from versions: none)
ERROR: No matching distribution found for planetary-system-stacker

 

Running 

 

➜  ~ python --version
Python 2.7.18
➜  ~ python3 --version
Python 3.9.7
➜  ~

 

and 

 

➜  ~ brew -v
Homebrew 3.3.6

 

on the newest Monterey, Macbook Air M1.

[Rolf]

My guess is that the problem ist the missing Matplotlib library. PSS depends on thai library. Could it be hat thais library is not available for thai particular OS version?

 

Sorry that I cannot be ob much help herr, but I habe no experience with Mac computers.

[Prutsky]

I can install Matplotlib pip:

pip3 install Matplotlib                        
Defaulting to user installation because normal site-packages is not writeable
Collecting Matplotlib
  Downloading matplotlib-3.5.0-cp38-cp38-macosx_11_0_arm64.whl (7.1 MB)
     |████████████████████████████████| 7.1 MB 5.6 MB/s            
Collecting pillow>=6.2.0
  Downloading Pillow-8.4.0-cp38-cp38-macosx_11_0_arm64.whl (2.8 MB)
     |████████████████████████████████| 2.8 MB 9.1 MB/s            
Collecting fonttools>=4.22.0
  Downloading fonttools-4.28.3-py3-none-any.whl (884 kB)
     |████████████████████████████████| 884 kB 9.2 MB/s            
Collecting cycler>=0.10
  Downloading cycler-0.11.0-py3-none-any.whl (6.4 kB)
Collecting kiwisolver>=1.0.1
  Downloading kiwisolver-1.3.2-cp38-cp38-macosx_11_0_arm64.whl (59 kB)
     |████████████████████████████████| 59 kB 10.4 MB/s            
Collecting packaging>=20.0
  Downloading packaging-21.3-py3-none-any.whl (40 kB)
     |████████████████████████████████| 40 kB 6.1 MB/s            
Collecting numpy>=1.17
  Downloading numpy-1.21.4-cp38-cp38-macosx_11_0_arm64.whl (12.3 MB)
     |████████████████████████████████| 12.3 MB 17.4 MB/s            
Collecting python-dateutil>=2.7
  Downloading python_dateutil-2.8.2-py2.py3-none-any.whl (247 kB)
     |████████████████████████████████| 247 kB 9.8 MB/s            
Collecting setuptools-scm>=4
  Downloading setuptools_scm-6.3.2-py3-none-any.whl (33 kB)
Collecting pyparsing>=2.2.1
  Downloading pyparsing-3.0.6-py3-none-any.whl (97 kB)
     |████████████████████████████████| 97 kB 10.2 MB/s            
Requirement already satisfied: six>=1.5 in /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/site-packages (from python-dateutil>=2.7->Matplotlib) (1.15.0)
Requirement already satisfied: setuptools in /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/site-packages (from setuptools-scm>=4->Matplotlib) (49.2.1)
Collecting tomli>=1.0.0
  Downloading tomli-1.2.2-py3-none-any.whl (12 kB)
Installing collected packages: pyparsing, tomli, packaging, setuptools-scm, python-dateutil, pillow, numpy, kiwisolver, fonttools, cycler, Matplotlib
  WARNING: The scripts f2py, f2py3 and f2py3.8 are installed in '/Users/prutsky/Library/Python/3.8/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  WARNING: The scripts fonttools, pyftmerge, pyftsubset and ttx are installed in '/Users/prutsky/Library/Python/3.8/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed Matplotlib-3.5.0 cycler-0.11.0 fonttools-4.28.3 kiwisolver-1.3.2 numpy-1.21.4 packaging-21.3 pillow-8.4.0 pyparsing-3.0.6 python-dateutil-2.8.2 setuptools-scm-6.3.2 tomli-1.2.2

So this can't be the problem, of?

Edited by Prutsky, 06 December 2021 - 07:55 AM.

[DeepSky Di]

As detailed in my posts above, I could only get PSS working with Python 3.8 on my Mac, which is an Intel MBP running Big Sur. The problem appears to be a numpy library whose devs changed a filename that broke apps that depend on it.

 

See posts 9 and 11 above.

[xploeris]

MacOS 10.14.6 (Mojave), Python 3.8.

PSS installed alright but when I try to run it gives up and I get this message:

Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.8/bin/planetarysystemstacker", line 5, in <module>
    from planetary_system_stacker.planetary_system_stacker import main
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/planetary_system_stacker/planetary_system_stacker.py", line 49, in <module>
    from alignment_point_editor import AlignmentPointEditorWidget
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/planetary_system_stacker/alignment_point_editor.py", line 34, in <module>
    from alignment_points import AlignmentPoints
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/planetary_system_stacker/alignment_points.py", line 32, in <module>
    from skimage.feature import register_translation
ImportError: cannot import name 'register_translation' from 'skimage.feature' (/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/skimage/feature/__init__.py)

 

Not a coder or super *nix geek so I'm not sure what the issue is, not even sure what would cause skimage.feature to be incomplete, or for PSS to be unable to import it, or whatever the cause is.

 

I tried Googling for hints and solutions but couldn't find anything helpful. Any ideas?

[Rolf]

Hi xploeris,

 

This problem seems to be related to a change in the „skimage“ library. They changed the name of the „register_translation“ function. I fixed that in a new PSS version (0.9.0) which I uploaded to PyPi the day before yesterday. I suggest you upgrade PSS to that version with

 

    pip install —upgrade planetary-system-stacker

 

I hope that helps.

 

All the best,

 Rolf

[xploeris]

That fixed the problem, thank you!

[DeepSky Di]

Hi xploeris,

 

This problem seems to be related to a change in the „skimage“ library. They changed the name of the „register_translation“ function. I fixed that in a new PSS version (0.9.0) which I uploaded to PyPi the day before yesterday. I suggest you upgrade PSS to that version with

 

    pip install —upgrade planetary-system-stacker

 

I hope that helps.

 

All the best,

 Rolf

Hi Rolf - what is the recommended version of Python for the current PSS? Apologies if this is somewhere in the notes, I just see "Python 3". As noted above, 3.9 didn't work when I was using PSS earlier this year, and I had to install 3.8.

[Rolf]

Hi DJL,

 

I recently installed a fresh Python 3.9 with the up-to-date versions of all the libraries required by PSS, both on Windows 10 and Ubuntu Linux 20.04. In both cases PSS worked flawlessly. So I removed all restrictions on the Python version on PyPI, and I recommend that users move to Python 3.9. If you have installed Python 3.9 some time ago, it is a good idea to upgrade all libraries.

 

Of course, if your PSS works properly with another Python version, there is no need to do a new Python installation.

 

All the best,

 Rolf

[RobertPettengill]

I didn't see a solution to this problem?  I'm having the same issue on an M1Max running Monterey 12.1

Then my own problem (and of a fellow amateur astronomer with an M1 Mac). 

If I install using

pip3 install planetary-system-stacker

 

I get this error

 

ERROR: Could not find a version that satisfies the requirement planetary-system-stacker (from versions: none)
ERROR: No matching distribution found for planetary-system-stacker

 

Running 

 

➜  ~ python --version
Python 2.7.18
➜  ~ python3 --version
Python 3.9.7
➜  ~

 

and 

 

➜  ~ brew -v
Homebrew 3.3.6

 

on the newest Monterey, Macbook Air M1.

Here is my output

rcp@Chaco ~ % python3                             
Python 3.9.9 (main, Nov 21 2021, 03:16:13)
[Clang 13.0.0 (clang-1300.0.29.3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>
rcp@Chaco ~ % pip3 install planetary-system-stacker
DEPRECATION: Configuring installation scheme with distutils config files is deprecated and will no longer work in the near future. If you are using a Homebrew or Linuxbrew Python, please see discussion at https://github.com/H...re/issues/76621
ERROR: Could not find a version that satisfies the requirement planetary-system-stacker (from versions: none)
ERROR: No matching distribution found for planetary-system-stacker
rcp@Chaco ~ % brew -v

Homebrew 3.3.9
Homebrew/homebrew-core (git revision fed2ce65f3d; last commit 2021-12-21)
Homebrew/homebrew-cask (git revision 041047ec39; last commit 2021-12-20)
rcp@Chaco ~ %

[DeepSky Di]

I see the issue.

 

When you command your Mac "python" in the terminal, it must respond by invoking python 3 not python 2. You won't be doing this explicitly but PSS will.

 

➜  ~ python --version
Python 2.7.18
➜  ~ python3 --version
Python 3.9.7

 

This indicates that Python 3 has been installed and will run in response to "python3" but "python" still invokes python2.

 

There are better or worse ways of dealing with this. What I did may make pythonistas recoil in horror.

 

    alias python python3

 

For better or worse, that worked for me. 

 

You can verify what version of python is going to run in response to "python":

 

    python --version

 

@Rolf - as you can see, not everyone is a python expert. One of the issues is that just installing python3 any version is insufficient for PSS to work, it has to be aliased to the python command as well. Is there a way for PSS to invoke python3 rather than python?

[DeepSky Di]

Further info. I updated my Mac's OS from Big Sur to Monterey.

 

Here is what I now get in response to "python"

 

WARNING: Python 2.7 is not recommended.
This version is included in macOS for compatibility with legacy software.
Future versions of macOS will not include Python 2.7.
Instead, it is recommended that you transition to using 'python3' from within Terminal.

Python 2.7.18 (default, Nov 13 2021, 06:17:34)
[GCC Apple LLVM 13.0.0 (clang-1300.0.29.10) [+internal-os, ptrauth-isa=deployme on darwin
Type "help", "copyright", "credits" or "license" for more information.

 

And in response to "python --version", I get python 2.17.18

 

And in response to "python3" I get python 3.8.12

 

Aaaaand the alias command didn't work.

 

Second semester of python masters degree starts here. Sigh.