You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When doing an initial install at NERSC, using either the release tag v1.0.0 or the current master, if I try to install all via python pip_sn_pack.py --action install --package=all it looks to me that only a small portion of the available packages are installed, like sn_pipe, but not sn_fit. Rather, I have to go back and add those other packages in separately - is that intended?
In a related item, I'll create a PR to update the NERSC install documentation to fix the reference to the jupyter kernel setup script which is actually named setup_kernel.sh rather than setup_nersc.sh
The text was updated successfully, but these errors were encountered:
no it is not intended. In principle the command python pip_sn_pack.py --action install --package=all should install all the packages.How did you get convinced that it was not the case? For instance, what is the result of the command 'python pip_sn_pack.py --action list'?
When doing an initial install at NERSC, using either the release tag v1.0.0 or the current master, if I try to install
all
viapython pip_sn_pack.py --action install --package=all
it looks to me that only a small portion of the available packages are installed, likesn_pipe
, but notsn_fit
. Rather, I have to go back and add those other packages in separately - is that intended?In a related item, I'll create a PR to update the NERSC install documentation to fix the reference to the jupyter kernel setup script which is actually named setup_kernel.sh rather than setup_nersc.sh
The text was updated successfully, but these errors were encountered: