No workers built for installed amuse packages

[sergio0711]

Describe the bug
I installed my AMUSE without any problem. However, when I tried to run an event-driven example calling the SeBa community code, it showed the next error:

exceptions.CodeException("The worker application does not exist, it should be at: \n{0}".format('\n'.join(tried_workers)))
amuse.support.exceptions.CodeException: The worker application does not exist, it should be at:
/Users/sergiosan/Amuse-env/lib/python3.9/site-packages/amuse/_workers/seba_worker
/Users/sergiosan/Amuse-env/lib/python3.9/site-packages/amuse/_workers/seba_worker
/Users/sergiosan/Amuse-env/lib/python3.9/site-packages/amuse/community/seba/seba_worker
/Users/sergiosan/Amuse-env/lib/python3.9/site-packages/amuse/rfi/seba_worker

I just realised that all the cummunity codes have their respective worker executable files, but the one from Seba is not there. I

Environment (please complete the following information):

• I have a MacBook Pro with M1 processor.

Am I missing something or I forgot to include the worker?

[rieder]

Hmm, that's odd. Could you post the output of

pip list | grep amuse

?

[sergio0711]

Completely odd.. It never happened to me. It's just missing that specific file.

When I do pip list | grep amuse I got all the community codes installed:

amuse 2023.3.0
amuse-athena 2023.3.0
amuse-bhtree 2023.3.0
amuse-bse 2023.3.0
amuse-capreole 2023.3.0
amuse-evtwin 2023.3.0
amuse-fastkick 2023.3.0
amuse-fi 2023.3.0
amuse-fractalcluster 2023.3.0
amuse-framework 2023.3.0
amuse-gadget2 2023.3.0
amuse-galactics 2023.3.0
amuse-galaxia 2023.3.0
amuse-halogen 2023.3.0
amuse-hermite 2023.3.0
amuse-hop 2023.3.0
amuse-huayno 2023.3.0
amuse-kepler 2023.3.0
amuse-kepler-orbiters 2023.3.0
amuse-mameclot 2023.3.0
amuse-mercury 2023.3.0
amuse-mmams 2023.3.0
amuse-ph4 2023.3.0
amuse-phigrape 2023.3.0
amuse-seba 2023.4.0
amuse-secularmultiple 2023.3.0
amuse-simplex 2023.3.0
amuse-smalln 2023.3.0
amuse-sphray 2023.3.0
amuse-sse 2023.3.0
amuse-twobody 2023.3.0

Including SeBa. Does it have something to do with the OS? On the other hand... Can I get the worker in any repository?

[rieder]

The worker should be built automatically when you install via pip, if it's not there the installation should fail.
The OS is not a problem either.
I just tested amuse-seba 2023.4.0 which you have installed, and I have the worker.

Could you try uninstalling amuse-seba
(pip uninstall amuse-seba),
then removing your pip cache files
(rm -r ~/Library/Caches/pip/wheels/*),
and then install amuse-seba again
(pip install --upgrade amuse-seba)?

[sergio0711]

I have applied the commands you proposed. After uninstalling SeBa I checked that the folder was properly removed, including the pip cache files. Finally, I re-install amuse-seba one more time but I'm getting the same folder without the worker. Definitely, very strange...

The only files that appear are:

• _ init _.py"
• _ pycache _ (folder)
• download.py
• interface.py
• version.py

[rieder]

And just to be sure, could you check that if you install e.g. amuse-sse it does have its respective worker?

[sergio0711]

Sure, I just even checked all other community code folders and there are more missing workers apart from SeBa. Those are:

• bhtree
• fi
• hop
• mmams
• simplex

Just in case, (if this info is relevant) my version of OS is Ventura and I installed the whole Amuse in my laptop in late February with python 3.9.

Also, last year my institute installed AMUSE in a cluster (Linux) with python 3.6. I checked folders and everything is in place.

[rieder]

Ok, so the problem is not Seba then, but more global.
I'm surprised that these packages install after failing to build the worker, that seems like the real bug here.

Your issue would then probably originate from a problem with the prerequisites, perhaps the compilers are not correct.
Did you upgrade anything after originally installing amuse-framework?
Could you attach the AMUSE config file (should be in /Users/sergiosan/Amuse-env/share/amuse/config.mk)?

Your OS and Python version are not a problem, I'm running the same.

[sergio0711]

For you first question. I haven't done any upgrade of AMUSE after installing it the first time. Just installed some libraries in python for my PhD project, particularly the one called Isochrones.

Now, here below I attached the file config.mk you asked me to look for (I added .txt at the end for uploading without format error)

config.mk.txt