kissplice2refgenome 2.0.2 old problems resurfacing

Question

[david.b.rombaut]

Hi,

Thanks for the new version for kiss2refgenome.

I just wanted to point out that all true/false in "Frameshift_?" have been reverted to what they were before 2.0.1 (or 2.0.0, I don't remember). So now, Frameshift_? == TRUE when there is no framshift.

EDIT: and while this "Frameshift_?" change is not really a problem, I found something that is a little more problematic. A few months ago I mentionned a problem of similarly identical events reported several times, here : Identical splicing events reported twice with KisSplice ?

The problem was resolved at the time, but it seems to be back with this new version. On the exact same data, running kiss2ref 2.0.2, and comparing with the result from 2.0.1, I have several thousands new events that are exact duplicate/triplicate/and more (except for the read coverage where the difference are something like 1 or 2 reads variations).

Considering the other post, this is likely : "a redundancy removal step has not been implemented in the latest version"

Thanks !

David.

Answer 1

[audric.cologne]

Hello David,

You are right, there was a big confusion with the project branches... I think everything is OK now, I posted a new K2RG version on the KisSplice website.

Thank you very much for your vigilance !

Bye, Audric

[david.b.rombaut]

Hello Audric,

I can confirm that everything is indeed ok.

Thanks for your work !

David