I'm sorry, I must be doing something obviously wrong. But after I install this, I cannot get afni to start (afni is not seen as a command). I tried to follow steps on the afni website seen on other installations (installed R, for example) but it is not clear to me what else I need to do in order to get afni to be a command and get the program to start. Thanks for the help.
Search Criteria
Package Details: afni 24.3.03-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/afni.git (read-only, click to copy) |
---|---|
Package Base: | afni |
Description: | An open-source environment for processing and displaying functional MRI data |
Upstream URL: | http://afni.nimh.nih.gov |
Licenses: | custom |
Submitter: | crmullins |
Maintainer: | liamtimms (keiichiiownsu12, ajschadler12) |
Last Packager: | ajschadler12 |
Votes: | 1 |
Popularity: | 0.000000 |
First Submitted: | 2016-06-29 01:28 (UTC) |
Last Updated: | 2024-10-21 17:18 (UTC) |
Dependencies (22)
- freeglut (freeglut-x11-gitAUR, freeglut-wayland-gitAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- glu (glu-gitAUR)
- gsl (gsl-gitAUR)
- libjpeg-turbo (mozjpeg-gitAUR, libjpeg-turbo-gitAUR, mozjpegAUR)
- libxft (libxft-gitAUR)
- libxmu
- libxpm (libxpm-gitAUR)
- openmotif
- python (python37AUR, python311AUR, python310AUR)
- r (r-mklAUR)
- tcsh (tcsh-gitAUR)
- xorg-server-xvfb (xorg-server-xvfb-gitAUR)
- r-afexAUR (optional)
- r-brms (optional)
- r-corrplotAUR (optional)
- r-lmertestAUR (optional)
- r-metaforAUR (optional)
- r-paranAUR (optional)
- r-phiaAUR (optional)
- Show 2 more dependencies...
Required by (2)
- afni-atlases (optional)
- python-nipype (optional)
Sources (4)
kcdah commented on 2021-05-05 20:31 (UTC)
liamtimms commented on 2021-05-05 15:50 (UTC) (edited on 2021-05-05 15:53 (UTC) by liamtimms)
@keiichiiownsu12 cheers, thanks. Do you think it would make more sense to try to include these in the default install from this AUR PKGBUILD or in a separate PKGBUILD? How much disk space are they taking after install (and unpacking?) on your machine?
For reference, here is the Neurodebian package I mentioned: https://neuro.debian.net/pkgs/afni-atlases.html?highlight=afni
The Arch "KISS" approach seems to imply these should probably be included here rather than separated out but if they end up being too massive it might make sense to keep them separate.
keiichiiownsu12 commented on 2021-05-05 03:25 (UTC)
REALLY wish they'd make this easier to find...: link to other atlas files
keiichiiownsu12 commented on 2021-05-02 23:33 (UTC)
@liamtimms looks like it's much simpler than either of us thought. There is a file called "atlases_latest", found here. After the files are extracted, if one places them in /opt/afni (or whichever location afni binaries are stored), the atlases are immediately available for use.
liamtimms commented on 2021-05-02 21:53 (UTC)
@keiichownsu12 I made a PKGBUILD for python-datalad
if you want to try to testing it with that afni_data repo.
liamtimms commented on 2021-05-01 19:52 (UTC) (edited on 2021-05-02 00:06 (UTC) by liamtimms)
hi @keiichiiownsu12 I'm actually not sure as I'm mostly using FSL for atlas fitting. There might be a flag as you suggest but it's not obvious from the documentation. You could try packaging a binary version of it and sharing it on the AUR, it seems like the binaries include the atlases based on the AFNI site.
Poking around a little I did just find this: https://github.com/afni/afni_atlases but I'm not sure why they have it "archived." It might be a good idea to check upstream to see what they recommend. If you can find out the best way to do it with that, I'd be happy to include an atlas download step in this PKGBUILD or you could make a separate AUR entry for the atlases (I think Neurodebian does this).
edit: looks like they have them over here now https://github.com/afni/afni_data it uses DataLad which we definitely should package for Arch if it hasn't been yet. Maybe that's the right place to start.
keiichiiownsu12 commented on 2021-04-30 23:36 (UTC)
How might I go about installing some of the default atlases afni is shipped with? E.g. the Talairach daemon. Is it a flag I need to set in the Makefile? Can I just download the atlas from the afni website and drop them into /opt/afni?
martin3141 commented on 2019-03-15 21:00 (UTC)
afni gui was complaining about the USE_LESSTIF flag not being enabled in compilation. I fixed this and made a few other minor changes to the package available from : https://github.com/martin3141/afni_arch
fishburn commented on 2018-03-09 20:39 (UTC)
Ran into a couple of issues: Current version is: 18.0.25 In build, "make" should be changed to "make all" I had to add the following to the beginning of package(): cd ${srcdir}/afni_src make install
Happy to add these changes if you want to make me a co-maintainer
Pinned Comments
liamtimms commented on 2022-05-10 20:27 (UTC)
AFNI releases get tagged with a frequency approaching individual git-commits (sometimes multiple times in one day). I update this package semi-regularly to keep it current but do not update it for every single AFNI release tag to avoid excessive burden on users. Please do not flag this package "out-of-date" without some technical justification. If the constant bleeding edge is required for your use case, I recommend using a
-git
package or using this PKGBUILD as a base and updating to each release tag yourself.ptaylor.afni commented on 2022-01-21 15:02 (UTC)
@keiichiiownsu12 :
Sure, workflow for reporting ArchLinux-AFNI issues could certainly go in that order (i.e., start this forum). I can also be pinged, too, though packaging questions will likely have to be dealt with by smarter folks...
Re. packaging: All the datasets for the distribution should just be in one places now (https://afni.nimh.nih.gov/pub/dist/atlases/atlases_current.tgz), whether you unpack+distribute it (which is what we do with the main distributions) or you ask people to get it separately. So, whatever you decide, hopefully it is simpler now.