libraries error

[rwatkins15]

Backstory: I'm installing ISIS4 on my machine so that I can run the Ames Stereo Pipeline. Installation seemed to go well. I downloaded the LRO mission data since I'm processing NAC images. I'm using a LINUX machine and have ISIS 4.2.0 installed.

I'm running the lronac2mosaic.py step in the ASP processing, and getting the following error:

lronac2isis from=M1132903462RE.IMG to=M1132903462RE.cub
lronac2isis from=M1132903462LE.IMG to=M1132903462LE.cub
Waiting for jobs to finish
lronac2isis: error while loading shared libraries: libarmadillo.so.9: cannot open shared object file: No such file or directory
lronac2isis: error while loading shared libraries: libarmadillo.so.9: cannot open shared object file: No such file or directory
lronaccal
lronaccal from=M1132903462RE.cub to=M1132903462RE.lronaccal.cub
lronaccal from=M1132903462LE.cub to=M1132903462LE.lronaccal.cub
Waiting for jobs to finish
lronaccal: error while loading shared libraries: libarmadillo.so.9: cannot open shared object file: No such file or directory
lronaccal: error while loading shared libraries: libarmadillo.so.9: cannot open shared object file: No such file or directory

So, I can't figure out how to fix this "shared libraries" error.

[dpmayerUSGS]

Possible duplicate of #4053

[rwatkins15]

thanks, I was just reading that one, I hadn't seen it before I submitted my issue!

[jessemapel]

I'm not sure if this is a duplicate of that or not. I'm going to be looking into this more today and hopefully find some answers.

[rwatkins15]

Thanks!

…

On Tue, Nov 3, 2020, 10:47 AM Jesse Mapel ***@***.***> wrote: I'm not sure if this is a duplicate of that or not. I'm going to be looking into this more today and hopefully find some answers. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJXJ65Z7NGMLVDLPTKQPC53SOAXZ3ANCNFSM4TI5SXPQ> .

[jessemapel]

@rwatkins15 This is not a duplicate of #4053, it looks like a different problem that is happening in Anaconda. For right now, can you try running conda install -c conda-forge armadillo=9.2 and see if it works then see below for correct comamnds. I'm going to put an issue in with Anaconda about this because it may be a bug there.

[jessemapel]

Sorry, bad conda command. Run conda install -c conda-forge armadillo=9.200 and then run conda install -c conda-forge gsl=2.6. That fixed this for me locally, but I'm still not sure what's causing this to occur in the first place.

[rwatkins15]

Ok that fixed the libraries error on my end too. I see another email from you with a command for adjusting my environment to match yours, should I run that as well?

…

On Wed, Nov 4, 2020 at 11:59 AM Jesse Mapel ***@***.***> wrote: Sorry, bad conda command. Run conda install -c conda-forge armadillo=9.200 and then run conda install -c conda-forge gsl=2.6. That fixed this for me locally, but I'm still not sure what's causing this to occur in the first place. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJXJ65ZVMDLWK2QDHV43OELSOGI6PANCNFSM4TI5SXPQ> .

-- ~ Ryan Watkins

[jessemapel]

No, don't run that other command, it won't do anything.

[rwatkins15]

Great, thanks! While I have you - I ran into an "issue" with spiceinit recently, where it was searching for a local kernel in the wrong directory. I figure this is a relatively easy fix, but is there somewhere in the command line where I indicate that it needs to search in a particular directory?

…

On Wed, Nov 4, 2020 at 1:25 PM Jesse Mapel ***@***.***> wrote: No, don't run that other command, it won't do anything. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJXJ655XSREVB3PMA4LFVFDSOGTBLANCNFSM4TI5SXPQ> .

-- ~ Ryan Watkins

[jessemapel]

@rwatkins15 You can specify where spiceinit should search for kernels for a mission by specifying your mission data directory in your isis preferences. Other than that, you can specify explicit kernels for spiceinit to use via its command line options.

[rwatkins15]

Thanks! Turns out I didn't run into that error this time around, so all of the fixes you sent and making sure I was running the correct version of ISIS seemed to do the trick.

…

On Wed, Nov 4, 2020 at 2:16 PM Jesse Mapel ***@***.***> wrote: @rwatkins15 <https://github.com/rwatkins15> You can specify where spiceinit should search for kernels for a mission by specifying your mission data directory in your isis preferences. Other than that, you can specify explicit kernels for spiceinit to use via its command line options. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJXJ653N5VLN33NKTTZS4DLSOGZAFANCNFSM4TI5SXPQ> .

-- ~ Ryan Watkins

[jlaura]

👍 I am going to close this particular issue as fixed. We are aware that the conda environments are having solving challenges in general and definitely appreciate hearing from users when those environment solves are causing this type of issue. Thank you for taking the time to write this up and interact.

We are working with the anaconda folks to figure out what else we can do to make installation of dependencies more consistent for everyone.

[rwatkins15]

Sounds great, thanks again! Hopefully the conda issues can get resolved soon - and thanks for the speedy responses!

…

On Wed, Nov 4, 2020 at 4:15 PM jlaura ***@***.***> wrote: 👍 I am going to close this particular issue as fixed. We are aware that the conda environments are having solving challenges in general and definitely appreciate hearing from users when those environment solves are causing this type of issue. Thank you for taking the time to write this up and interact. We are working with the anaconda folks to figure out what else we can do to make installation of dependencies more consistent for everyone. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJXJ655WEHRZCO53LYZ3RDDSOHG6TANCNFSM4TI5SXPQ> .

-- ~ Ryan Watkins