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

agat_sp_manage_IDs.pl not sorting properly fix #411 #415

Merged
merged 3 commits into from
Jan 12, 2024
Merged

agat_sp_manage_IDs.pl not sorting properly fix #411 #415

merged 3 commits into from
Jan 12, 2024

Conversation

Juke34
Copy link
Collaborator

@Juke34 Juke34 commented Jan 12, 2024

No description provided.

… starting further being set earlier in the file due to super high end value) + Change level2 sorting for print_omniscient_as_match
@Juke34
Copy link
Collaborator Author

Juke34 commented Jan 12, 2024

@kashiff007 @Neato-Nick could you give a try of that version? I should be fine by now

# clone the repo 
git clone [email protected]:NBISweden/AGAT.git
# move into the rep 
cd AGAT
# move into that branch 
git checkout 411
# --- test the script ---
# A) either you do the installation and run the command
make
make install
agat_sp_manage_IDs.pl --gff in ...
# B) or you run directly the command (without installing that version in hard in your computer)
perl -I lib bin/agat_sp_manage_IDs.pl --gff input ...

@Neato-Nick
Copy link

@Juke34 you are a magician. The fix absolutely works. I've been using AGAT for three years, and I recommend this software to everyone I know. This is only my second bug and you fixed both in less than a day. Thank you for being so responsive and quick!

@Juke34
Copy link
Collaborator Author

Juke34 commented Jan 12, 2024

Thank you for your feedback

@Juke34 Juke34 merged commit 703106c into master Jan 12, 2024
3 of 5 checks passed
@Juke34 Juke34 deleted the 411 branch January 12, 2024 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants