-
Notifications
You must be signed in to change notification settings - Fork 180
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
Running Hi-C pro yields no results #400
Comments
Hi, |
Yes, of course. amzaleg@discovery2:~/new/amzaleg/hichip$ tree raw_data |
ok. So update the config file with ;
These options allow to detect R1 and R2 files using a single regexp. |
Thank you so much.
|
could you check if you have an error message in |
you did not provide the bowtie2 index in your conf ! |
thank you so much for your prompt responses! I'll send you my updated config file as well as how the directory with my hg19 bowtie2 indices look. |
I know that's a bit unclear but actually bowtie2 indexes are detected by a concatenation of BOWTIE2_INDEX_PATH and REFERENCE_GENOME ...
|
Thank you so much! It seems to be running now. I appreciate all your help. |
Hello! #!/bin/bash /home1/amzaleg/new/amzaleg/hichip_tools/HiC-Pro-2.11.4/bin/HiC-Pro -i ~/new/amzaleg/hichip/raw_data -o ~/new/amzaleg/hichip/run/new_output -c ~/new/amzaleg/hichip/run/config-hicpro.txt -s mapping -s proc_hic |
Hi,
In this case, all chunks will be processed in parallel and then merged before building the contact maps. Best |
Just a quick clarification: I was able to do the split to 10 million chucks for every fastq file. When you say "put all the chunks in the same output folder" I put split files for both pairs of the fastq files for each condition in a separate directory. I then ran the parallel command directing the input files to where the directory of all split files are. Whe I ran the parallel code I got the both .sh files to run via SLURM. I'm just concerned that I'm doing something wrong because the split files look like this: ├── GM_rep1 After I ran the part 1 .sh file yielding this result : ├── 00_GM_HiChIP_H3K27Ac_rep1_1_hg19_bt2.bwt2glob.bam with some of those files being empty. Is this what you had in mind? |
Hi |
Hi, In MyLa_rep2 there should be split files from 0-21, but only 10-21 are in the btw2 folder. |
So I checked the logs for that replicate looking at one of the chunks that were missing and this was the error in the file ##HiC-Pro mapping |
never seen that before ! it seems to be an internal bowtie2 error ... |
That's weird as it didn't happen to any of my other samples (or even all the chunks for that replicate)! I'll do some investigating. Thank you for your help! |
http://seqanswers.com/forums/showthread.php?t=5318 "These types of errors occur when the files are genuinely either corrupt or incomplete (e.g. if the disk becomes exhausted during the index-building process). Can you send detailed output from one example where this happens, including a 'ls -l' on the index files after bowtie-build completes?" |
Maybe you can check if the files which crashed are complete (reads/qualities) or try to realign one of them manually, to see if you can reproduce the error |
It works! Thank you very much :) |
Hello,
I'm trying to run perform a HiChIP analysis -which takes principles of ChIP and Hi-C to determine interactions between genomic loci. I'm trying to run Hi-C Pro in published data to make sure I know how to perform the analysis before proceeding to mine. Basically I've made sure to have the fastq files in a particular directory (each individual sample has it's own directory within the major fastq directory). I've also filled out the config-hicpro.txt. When I try to run the command I see that in my output directory I now have a symbolic link to my raw data (called rawdata) and a new configuration file (with the same name). Nothing seems to be running and I'm stuck. Can you help me out?
the code I'm running:
/home1/amzaleg/new/amzaleg/hichip_tools/HiC-Pro-2.11.4/bin/HiC-Pro -i ~/new/amzaleg/hichip/raw_data -o ~/new/amzaleg/hichip/run/new_output -c ~/new/amzaleg/hichip/run/config-hicpro.txt -s mapping -s proc_hic
I'll also attach my configuration file
config-hicpro.txt
The text was updated successfully, but these errors were encountered: