tin score calculation does not produce proper output for >1 bamfiles provided
AngryMaciek opened this issue · comments
Describe the bug
An issue we discovered with @mkatsanto today.
If you specify >1 input BAMfile to the script the output table still contains scores only for the first sample provided.
Requires a closer look at the paralilization and inspection where the scores are lost/overwritten.
To Reproduce
Run the test from the CI but adjust the command so that you specify two times the same input bam file.
Expected behavior
The output table should contain quantified TIN scores for two samples.
Additional context
We usually run this just for 1 input BAM file, but the original script contained the functionality that one may in fact provide multiple samples. Please see the script parameters specification for more info. However, it seems that this functionality is broken now.