{"action":"created","issue":{"url":"https://api.github.com/repos/gpertea/stringtie/issues/32","labels_url":"https://api.github.com/repos/gpertea/stringtie/issues/32/labels{/name}","comments_url":"https://api.github.com/repos/gpertea/stringtie/issues/32/comments","events_url":"https://api.github.com/repos/gpertea/stringtie/issues/32/events","html_url":"https://github.com/gpertea/stringtie/issues/32","id":122162854,"number":32,"title":"Error at GBitVec: index out of bounds","user":{"login":"ls233","id":717964,"avatar_url":"https://avatars.githubusercontent.com/u/717964?v=3","gravatar_id":"","url":"https://api.github.com/users/ls233","html_url":"https://github.com/ls233","followers_url":"https://api.github.com/users/ls233/followers","following_url":"https://api.github.com/users/ls233/following{/other_user}","gists_url":"https://api.github.com/users/ls233/gists{/gist_id}","starred_url":"https://api.github.com/users/ls233/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ls233/subscriptions","organizations_url":"https://api.github.com/users/ls233/orgs","repos_url":"https://api.github.com/users/ls233/repos","events_url":"https://api.github.com/users/ls233/events{/privacy}","received_events_url":"https://api.github.com/users/ls233/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-12-15T00:17:33Z","updated_at":"2015-12-16T12:31:54Z","closed_at":null,"body":"I'm getting this error message when running stringtie V1.1.1 in the \"-G\" regime.\r\nError at GBitVec: index 391265981 out of bounds (size 391265970)\r\n\r\nAny ideas?"},"comment":{"url":"https://api.github.com/repos/gpertea/stringtie/issues/comments/165092389","html_url":"https://github.com/gpertea/stringtie/issues/32#issuecomment-165092389","issue_url":"https://api.github.com/repos/gpertea/stringtie/issues/32","id":165092389,"user":{"login":"gpertea","id":3372619,"avatar_url":"https://avatars.githubusercontent.com/u/3372619?v=3","gravatar_id":"","url":"https://api.github.com/users/gpertea","html_url":"https://github.com/gpertea","followers_url":"https://api.github.com/users/gpertea/followers","following_url":"https://api.github.com/users/gpertea/following{/other_user}","gists_url":"https://api.github.com/users/gpertea/gists{/gist_id}","starred_url":"https://api.github.com/users/gpertea/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gpertea/subscriptions","organizations_url":"https://api.github.com/users/gpertea/orgs","repos_url":"https://api.github.com/users/gpertea/repos","events_url":"https://api.github.com/users/gpertea/events{/privacy}","received_events_url":"https://api.github.com/users/gpertea/received_events","type":"User","site_admin":false},"created_at":"2015-12-16T12:31:54Z","updated_at":"2015-12-16T12:31:54Z","body":"Any chance of sharing with us the data which trigger this error? If you run with -v option (and no multi-threading) it should be possible to identify the bundle and the genomic location where the error happens and it should make it possible to extract only the reads and the reference transcripts from that location which triggers the problem. If you agree to share those data for debugging, please contact me at gpertea@jhu.edu to further discuss the data transfer details (unless you can already extract it and upload it somewhere for me to retrieve).\r\nThanks!"}}