Kang Hu

Hi @wjq1981, I just wanted to provide you with an update on the recent run of HiTE with your 9GB genome. There was a minor hiccup during the process. The...

Hi @xiekunwhy, Thank you very much for your suggestions—you’ve done a lot of great work, and I wish you all the best. Our design goal is to make HiTE as...

Hi @wjq1981, I’ve just updated the code. Please download the latest code. You can now follow the tutorial below to run HiTE for large genome annotation: [https://github.com/CSU-KangHu/HiTE/wiki/Running-HiTE-for-Large-Genome-Annotation](https://github.com/CSU-KangHu/HiTE/wiki/Running-HiTE-for-Large-Genome-Annotation) Best regards, Kang

Thank you for your kind reply. I’m delighted to hear that HiTE has been helpful to you!

Hi @shandows, You're absolutely right — your approach is correct. We had modified the parameters but forgot to update them in the Nextflow script. Thanks for pointing it out!

I believe this is the main issue: ``` .command.run: line 147: /dev/null: Permission denied ``` In panHiTE, many command outputs are redirected to `/dev/null`. You can check `/filer-5/agruppen/PBP/tan/software/HiTE/work/97/93962bab7f1c676d2c1b7c303fffac/preprocess_genomes.log` for more...

You can install it via Conda, as the Singularity and Docker images may not be updated in a timely manner. If you install through Conda, you can use the `--work_dir`...

Hi @zbh200937, Could you please share the complete output log? Additionally, I’d like to know the size of the genome. If possible, it would be helpful if you could provide...

Hi @zbh200937, Based on the download link you provided, I tested the largest genome file, **ZJ.chrom.fasta** (3.1 GB). Since panHiTE internally calls HiTE for each genome, I ran HiTE separately...

It's possible that the program did not complete successfully. You can check the `.nextflow.log` file to locate the `work_dir` corresponding to the problematic genome process. Then, go into that `work_dir`...