-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sh: 1: source: not found when calling make_volumetric_ggseg() #57
Comments
Hey. This originated in the freesurfer R package, not from this package it self. I'm not the best to answer why its sourced, but from my experience, its very much needed to make the freesurfer functions be available to your R session to call upon. https://github.com/muschellij2/freesurfer/blob/master/R/mri_convert.R @muschellij2 I dont know if you might have some illuminating input into why this would not work on Ubuntu? |
You're quoting aseg2 <- make_volumetric_ggseg(
label_file = file.path(freesurfer::fs_subj_dir(), "fsaverage5", "mri/aseg.mgz"),
vertex_size_limits = c(10, NA)
) |
ah @muschellij2 thanks for seeing that! I didnt notice the quotation marks. |
Hi all, First I want to say thanks for making this package. Second, I am trying to create a 3d subcortical atlas used the aseg2_3d command, following instructions here
Aslo get an sh: 1: source: not found error, using Ubuntu 22.04.3 LTS and R 4.3.2 Not using any quotations |
Did this run? The Can you try |
It did not run, here is the error message I get, even after adding the suggested option:
|
I have a kind of full January already, but I'll try diving into this asap. Any chance you can provide the mgz and lut for me, so I have the same data to test on? |
Thank you! Sure, attached. FYI, here is the python code I used to make the .mgz (ANTsPy)
Then using freesurfer:
Original atlas file can be found here. |
Hello,
when calling
I get
Obviously, sh doesn't know the source command - but why is sh used? in FreeSurferEnv.sh first line is #!/bin/bash -p.
System: Ubuntu 22 running newest RStudio Server.
Thank you very much!
The text was updated successfully, but these errors were encountered: