Closed brentwilder closed 1 year ago
Thank you for your report. I tried, and ASP 3.1.0 installs for me. I wonder if you can run, per the documentation:
conda config --show channels
and see what it shows. It should show
channels:
It shows something else, you can try to first run:
conda config --env --add channels conda-forge conda config --env --add channels usgs-astrogeology conda config --env --add channels nasa-ames-stereo-pipeline
and then show the channels again.
Then I ran
conda create -n asp python=3.6
conda activate asp
conda install stereo-pipeline==3.1.0
I tried this on RedHat 7.9, but I doubt the precise OS version is important.
I also tried creating a separate installation with the command:
conda create -n asp2 stereo-pipeline=3.1.0
and it worked too.
If you have no luck with the above, let me know and I can try to think of something else.
To add, I tried this on Ubuntu 18.04.6 LTS and it worked too.
Hi Oleg, thanks for your response. The channels and the priority looks correct when running conda config --show channels
.. Could this be related to this issue on USGS-Astrogeology (https://github.com/USGS-Astrogeology/ISIS3/issues/3570)?
This should not be related to that. Here you are making a brand new environment.
I am not sure what can be done since I can't reproduce the issue.
You can try installing isis 6 first, and see if that one works. Then try to add visionworkbench and if no problems then also asp itself.
Or you can try another Linux machine.
The odd thing is that it is not clear from your error message which packages have the conflict.
On Mon, Jul 18, 2022, 8:27 AM Brent Wilder @.***> wrote:
Hi Oleg, thanks for your response. The channels and the priority looks correct when running conda config --show channels.. Could this be related to this issue on USGS-Astrogeology (USGS-Astrogeology/ISIS3#3570 https://github.com/USGS-Astrogeology/ISIS3/issues/3570)?
— Reply to this email directly, view it on GitHub https://github.com/NeoGeographyToolkit/StereoPipeline/issues/372#issuecomment-1187641514, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKDU3DGAWSMXLJPGPHY52DVUVZVHANCNFSM5327JEQQ . You are receiving this because you commented.Message ID: @.***>
Okay, sounds good. I'll give this a try when I get back to my computer later tonight.
So I got it to work! It turns out that it only works when I use compatible MiniConda Installer with my base python 3.8 on my computer (makes sense). Originally I was just downloading the first Latest Miniconda Installer for Linux... Sorry for the confusion.
That is some quirky conda behavior. I would have thought that the only thing that mattered is that the environment ASP is installed in is Python 3.6 (per our doc), and what the rest of your conda or system versions has should not be important.
@oleg-alexandrov Agreed, really strange.
@brentwilder When you activate the environment and echo your PATH, what is the output? I wonder if conda is not prepending the path properly, so the system python is being picked up? That is the only thing that springs to mind about how your system python could be even seen.
@oleg-alexandrov @jlaura I wiped miniconda3 and experimented with both conda .sh installers. _Now both_ are successfully able to install ASP==3.1.0... Not sure what was conflicting before because I unfortunately can't recreate the error I was getting earlier this week... The only thing I can think of was that I installed glibc-source
in an effort to see if my system was outdated for miniconda... Which may have fixed it? At any rate, this was 100% a conda issue that was specific to my machine, so don't want to take any more of your time! Here are some outputs from my experiment tonight:
Strange output when first installing...
brent@XPS-15-9570:~/Downloads$ conda activate asp
CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
To initialize your shell, run
$ conda init <SHELL_NAME>
Currently supported shells are:
- bash
- fish
- tcsh
- xonsh
- zsh
- powershell
See 'conda init --help' for more information and options.
IMPORTANT: You may need to close and restart your shell after running 'conda init'.
brent@XPS-15-9570:~/Downloads$ conda init bash
no change /home/brent/miniconda3/condabin/conda
no change /home/brent/miniconda3/bin/conda
no change /home/brent/miniconda3/bin/conda-env
no change /home/brent/miniconda3/bin/activate
no change /home/brent/miniconda3/bin/deactivate
no change /home/brent/miniconda3/etc/profile.d/conda.sh
no change /home/brent/miniconda3/etc/fish/conf.d/conda.fish
no change /home/brent/miniconda3/shell/condabin/Conda.psm1
no change /home/brent/miniconda3/shell/condabin/conda-hook.ps1
no change /home/brent/miniconda3/lib/python3.9/site-packages/xontrib/conda.xsh
no change /home/brent/miniconda3/etc/profile.d/conda.csh
no change /home/brent/.bashrc
No action taken.
$ echo PATH: /home/brent/miniconda3/envs/asp/bin:/home/brent/miniconda3/condabin:/home/brent/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
$ python --version: Python 3.6.13
$ conda --version: conda 4.12.0
$ echo PATH: /home/brent/miniconda3/envs/asp/bin:/home/brent/miniconda3/condabin:/home/brent/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
$ python --version: Python 3.6.13
$ conda --version: conda 4.12.0
Glad things worked. What you are showing now are pretty standard prompts from conda. I don't see anything unusual. After you go through these, and restart your shell, you should be able to use conda.
Describe the bug I've had no issue using the precompiled binaries in the past, but yesterday I found out from a colleague that ASP could also be built via conda. However, when I tried to set this up on my computer it seems that conda was unable to navigate package conflicts successfully.
To Reproduce Steps to reproduce the behavior:
Expected behavior Conda builds environment with Ames Stereo Pipeline v.3.1.0
Your Environment (please complete the following information):
Error Logs, Terminal Captures, Screenshots The following is just the last trailing outputs from the terminal from both steps 1-3 above.