Closed ClaudeHu closed 3 months ago
One of your chromosomes doesnt seem represented in the chrome sizes hashmap. Not immediately sure the solution... however...
You should probably be running with the --release
flag. Or running cargo build --release
. Then running the binary. It drastically speeds things up
I added a better error message for this situation as well as a test condition.
It appears as though the original uniwig would not error in this situation. It would instead ignore/skip these chromosomes, but it would not alert the user while doing so. Do we actually want to replicate that behavior? Or should it be left as is, where the user must remove unlisted chromosomes when using a chrom.sizes file?
Make this a warning and just have it continue.
Ok, this has been changed to a warning and pushed to dev branch.
Should we just do a release? I guess its not crazy important right now and you can just build from source if truly needed
Uniwig still doesn't have python bindings yet.
Run
uniwig
with this command:caused this error(RUST_BACKTRACE=full):
The combined BED file and chrom.size file are attached in the format of txt.
chrom_sizes.txt combined_chrsort.txt