dputhier
commented
6 years ago Whoua. So nice. I will try it asap (and don't know how we will deal with this new kind of GTF without transcript/gene IDs). Wait and see. This will be in the future (not the upcoming) release. I'm currently ending some refactoring to delete any R dependencies. It is on the way and already finished (it is a matter of few hours now). Then I will check select_transcript and go for a release version. The last thing we have to do is to refactor a little bit the git repository of libgtftk. Here is the model used by git flow:
https://datasift.github.io/gitflow/IntroducingGitFlow.html
The idea is simply to have a master branch that mirrors the current release (tagged) and a develop branches from which feature branches are starting. Making a release is even more simplified using hub flow:
https://datasift.github.io/gitflow/GitFlowForGitHub.html
Best
Hello, I wanted to do funny things before holidays, so I did a function to load blast results. Here is the signature :
GTF_DATA *load_blast(char *input)As you can see, it takes a blast result file name in parameter and returns a GTF_DATA pointer. Of course, there is no gene_id or transcript_id attribute ... Let me know if you try it !