For some reason, anaconda/MacOS users have problems compiling with gfortran/numpy.f2py. I have encountered this problem over the years and I do not have any idea why is happening. Perhaps one must ping the Anaconda developers and ask for help.
During installation or when first time powering the Exo-Striker, one usually gets:
ImportError: cannot import name 'rvmod_for' from partially initialized module 'RV_mod.rvmod' (most likely due to a circular import)
The problem is that numpy.f2py cannot create the rvmod*.so library, because the gfortran does not work as it should....
The solution is to get out from the Conda environment:
$ conda deactivate
Then install the tool with your default python3.
Once the rvmod*.so is compiled, I think the Anaconda users can use the Exo-Striker without problems.
For some reason, anaconda/MacOS users have problems compiling with gfortran/numpy.f2py. I have encountered this problem over the years and I do not have any idea why is happening. Perhaps one must ping the Anaconda developers and ask for help.
During installation or when first time powering the Exo-Striker, one usually gets:
ImportError: cannot import name 'rvmod_for' from partially initialized module 'RV_mod.rvmod' (most likely due to a circular import)The problem is that numpy.f2py cannot create the rvmod*.so library, because the gfortran does not work as it should....
The solution is to get out from the Conda environment:
$ conda deactivateThen install the tool with your default python3.
Once the rvmod*.so is compiled, I think the Anaconda users can use the Exo-Striker without problems.