You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changed 32-bit int to 64-bit int when getting number of mapped reads to avoid overflow when displaying progress of how many reads have been mapped. Resolves issue #8
Fixed specifying @no-chain in the config file (previously, it was not being recognized). Thanks to @bentyeh for pointing out this bug.
Allow no-chain to take in arguments about what should be chained vs not chained (e.g. specifying @no-chain x,y means no-chain only applies to the extraction/UMI-like string named x and the extraction/UMI-like string named y; others will still be chained together during the extraction).
Only update in this release: when using minFinds or minFindsG without --assign, the reads that don't mean the min finds criteria will be thrown out (previously, without --assign, those options didn't do anything unless the keep or discard options were supplied).