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

Improve details on installation #1

Open
jpinedaf opened this issue Sep 30, 2019 · 1 comment
Open

Improve details on installation #1

jpinedaf opened this issue Sep 30, 2019 · 1 comment

Comments

@jpinedaf
Copy link

I am trying to install the package, however, it is not well documented what needs to be modified. I guess that this is the suggested method:

python setup.py install --user

However, this must be modified in the setup.py file

MNEST_DIR = Path('/users/bsvoboda/code/MultiNest')

maybe use the LD_LIBRARY_PATH variable.

Also, if I need to use the icc compiler instead of gcc, then this command line could be used:

LDSHARED="icc -shared" CC=icc python setup.py install --user

also, I think that -openmp should be removed from setup.py in the case of using icc

How do you setup the code for a new dataset? What is the shortcut?

@autocorr
Copy link
Owner

autocorr commented Apr 5, 2020

Hi Jaime, I've updated the installation instructions in the README. For right now, I recommend cloning the repo, editing the setup.py file with your preferred compiler directives, running make, and then adding the directory to your Python path. I would recommend this over installing it your environment's site-packages mostly because you will almost certainly need to modify something, and you might find that easier to do that on a separate git branch compared to repeatedly re-installing it whenever a change is made.

Note that I added an environment variable for the MultiNest directory MNEST_DIR. Hard-coded pathes should now be removed, but some relative paths and un-tracked data files exist that I use for testing (like nestfit.main.get_test_cubestack or nestfit.main.test_fit_cube).

I'm fairly inexperienced with Python packaging and distribution however, so any tips are welcome. The setup.py pile is mostly for building the extension module rather than installing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants