AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

|
January 19, 2021 04:25PM
Hi-

I think we have resolved the issue now.

I believe it was that PYTHONPATH was explicitly set in the ~/.bashrc file, pointing to an old (non-conda) location of Python on the system. Especially when only the base Python (which was version 3.*) was used, that was causing some confusing (because the older version pointed to was version 2.7).

Commenting out the PYTHONPATH value helped.

In each of the ~/.bashrc and ~/.cshrc, then, there was the "conda initialize" block of code for that shell, and then also a line following that with "conda activate [name of desired environment]". Then things appear to be working.

*Additional note: the PyQt4 issues in the above afni_system_check outputs are not important; we don't use PyQt4 for anything at the moment (and it also has installations in Python ver 3.*, anyways).

--pt
Subject Author Posted

tcsh vs. Miniconda

annschoe January 18, 2021 04:33PM

Re: tcsh vs. Miniconda

ptaylor January 18, 2021 08:25PM

Re: tcsh vs. Miniconda

annschoe January 18, 2021 11:59PM

Re: tcsh vs. Miniconda

ptaylor January 19, 2021 09:09AM

Re: tcsh vs. Miniconda

annschoe January 19, 2021 11:33AM

Re: tcsh vs. Miniconda

ptaylor January 19, 2021 04:25PM