Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

blast2gtf #81

Open
fafa13 opened this issue Jul 19, 2018 · 1 comment
Open

blast2gtf #81

fafa13 opened this issue Jul 19, 2018 · 1 comment

Comments

@fafa13
Copy link
Collaborator

fafa13 commented Jul 19, 2018

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 !

@dputhier
Copy link
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants