Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MultiProcessing Bug with M1 Pro chipped Mac books #104

Open
daxfeliz opened this issue Oct 6, 2022 · 2 comments
Open

MultiProcessing Bug with M1 Pro chipped Mac books #104

daxfeliz opened this issue Oct 6, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@daxfeliz
Copy link

daxfeliz commented Oct 6, 2022

Describe the bug
Upon a fresh installation of TLS on a Macbook Pro (Version 12.3 with Apple M1 Pro chip), whenever the transitleastsquares "power" function is ran, a seemingly infinite loop of processes is created. I suspected this is due to how Python tries to handle multi-processing and the newer Mac processor is no longer using a Intel x86_64 processor but instead a ARM-based processor.

To Reproduce
Steps to reproduce the behavior:
Following the K2-3b tutorial (https://github.com/hippke/tls/blob/master/tutorials/02%20Starter's%20guide%20-%20K2-3b%2C%20a%20red%20dwarf%20with%20a%20planet.ipynb) regularly produces this issue when ran from a command terminal.

Desktop (please complete the following information):

  • OS: MacOS (Version 12.3)
  • Python version 3.9.12
  • TLS Version [1.0.31]

Possible solution?
In the "main.py" scripy within transitleastsquares, if importing "multiprocess" (which requires a pip installation) instead of Python's default "multiprocessing", this seems to work without having to change anything else.

@daxfeliz daxfeliz added the bug Something isn't working label Oct 6, 2022
@hippke
Copy link
Owner

hippke commented Oct 11, 2022

Sorry for that. I've been struggling with similar incompatibilities in another project. Unfortunately I don't have an M1 Mac (only AMD and Intel) so it's hard for me to find a solution that works on all platforms. Can you check your fix with use_threads=1 and use_threads=10 (or whatever your machine has)? I'd like to make sure that it scales well with that package, before making the change.

@alerogex
Copy link

Hi, I am encountering the same issue. Same TLS version, Python 3.9.16, MacOS 14.1.2 (again M1 chip). Since this issue was opened more than one year ago, I wondered whether a solution has been found or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants