Ampliconclip report#2039
Conversation
|
Seems like there is something up with github's checking for mergability being too slow for appveyor to know that it can run. Is it possible to manually trigger the appveyor test? It did succeed for an earier commit (348619e) |
|
@whitwham : i think this is ready for review now |
|
@bwlang I'll take a look next week when I'm back in the office. Thanks. |
|
looks like the ubuntu build is failing due to configure's c compiler test. I think that's unrelated to this code. |
|
Thanks. I'm testing a cirrus-ci change to fix this in htslib and if that cures it I'll migrate it over to the other packages too. It looks like Ubuntu broke their latest clang build. :( |
|
looks like htslib is still failing, but in a different way now |
|
Hi @bwlang, let me know when you are ready for me to review and merge this PR. Thanks. |
|
@whitwham I think it's ready for your feedback now. Hopefully the htslib issue we see from the build systems will get resolved soon too. |
| for (int i = 0; i < sites->length; i++) { | ||
| fprintf(bed_count_summary_fp, "%s\t%"PRId64"\t%"PRId64"\t%s\t%s\t%s\t%"PRId64"\n", | ||
| kh_key(bed_hash, itr), sites->bp[i].left, sites->bp[i].right, sites->bp[i].name, | ||
| sites->bp[i].score, (sites->bp[i].rev ? "-" : "+") , sites->bp[i].num_reads); |
There was a problem hiding this comment.
bp[i].rev can be uninitialised if the --strand option is not used.
There was a problem hiding this comment.
I've added this, but i think it's a bit strange that we modify the bed information... though this does accurately describe the count (which is not stranded now)
char* strand_out = param->use_strand ? (sites->bp[i].rev ? "-" : "+") : ".";
I could change the struct to store a char instead of rev (more invasive, but maybe nicer than an int ?)
There was a problem hiding this comment.
The rev in the struct is used by ampliconstats as well as ampliconclip so I would prefer not to change it.
You could add another member to the structure to store the strand symbol (if present).
There was a problem hiding this comment.
Do you think it's better to
- store the char in the struct (which could in theory be out of sync with rev)
or - recalc like this and switch the strand column to '.' indicating that the count is unstranded ?
(i implemented # 2, but not sure if that's best).
There was a problem hiding this comment.
Hmm, leave it the second way for now. I can always change it later if need be.
|
Good, apart from the comment I added. If you could squash the commits down to a more reasonable number that would be great. |
|
Also, rebasing should help with the failed test. |
|
looks like it still can't configure htslib. |
ef3ae41 to
7f393fa
Compare
|
@whitwham |
|
@bwlang Yes, but I have been distracted by non samtools work. I should have time to look at it today. |
…trand is used. Updates expected test results
7f393fa to
a6b9501
Compare
|
Thank you. I rebased and force pushed to make the tests work again. |
|
@daviesrob |
fixes #2033