-
Notifications
You must be signed in to change notification settings - Fork 28
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
access to genome dir? #6
Comments
Sorry you are having trouble. How did you edit your settings.txt? Can you share the file here? Is this only a problem for hg19 or does it happen for hg38 as well? |
I edited it through filezilla. File attached. and yes just tried with hg38 and still having the same problem. Thanks! |
That looks okay. Just to confirm, you ran the Can you also share the complete log file where the error is? |
Yes! ChIP route worked great. Here are the log files. Also attaching the peaks-macs in case? slurm-17597688.txt |
I also tried to copy your hg19 to the folder im running these analyses in and set that as the genome-dir but that also didn't work |
I didn't notice it earlier, but if you look at the error message, you'll see it spans two lines because there is a line break after hg19. It looks like the problem is you have non-UNIX line endings. When you edited the file, you probably introduced those. You can check for yourself with To fix, run:
|
that worked great! thanks! |
Great! The samples CSV files get cleaned up by default. The settings.txt does not, but usually it is not edited, so you are less likely to run into any issues. I should fix that. |
Hello! I'm having a small issue with the ChIP seq peak calling. The first ChIP route worked great. I'm in the same folder and manually edited the samples.pairs.csv with IPs and inputs. I've updated the settings.txt accordingly and I'm still met with :
peaks-macs.sh ERROR: genome dir /gpfs/data/igorlab/ref/hg19
does not exist
I can see I have access to the folder however. Is there a permissions setting? I'm new to this so I'm sure I'm missing something.
Thanks for your time!
The text was updated successfully, but these errors were encountered: