Closed dsb66 closed 1 month ago
Exact same issue as here: https://github.com/pachterlab/kb_python/issues/251
If you create your reference with kb ref and use those files directly, it should work. Your t2g file (and -c1 and -c2 files) needs to exactly match what's in your index. If it hangs, that means it doesn't match.
In general, if bustools count takes over 20 minutes, you should probably just kill the process because it's hanging.
Thanks, I missed that issue. I had both the standard and nac indexes in the same directory and that must have messed up one of the nac files. I rebuilt the nac index and know everything is fine.
Describe the issue kb count of 1.6B 10X reads runs for days (run not completed yet) on a 16-thread computer. Based on my previous experience and the run time statement in your preprint, the run should have been completed in less than 2 hours. The verbose output pasted below was started yesterday, but the same command (not in verbose mode) has been running for one week.
The
kb count
part of the pipeline completes in ~1 hour, then the program keeps runningbustools counts
with no output accumulating in thecounts_unfiltered
directory (the files in the directory remains of size 0 bytes).The run_info.json output is below:
What is the exact command that was run?
Command output (with
--verbose
flag)