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

Feature request: gat-compare should not assume the "track" column is equal to "merged" #3

Closed
skiaphrene opened this issue Sep 6, 2016 · 1 comment
Assignees

Comments

@skiaphrene
Copy link

Dear Andreas,

I have been happily using GAT (gat-run & gat-compare) over the past months - thanks a lot for it!

I recently updated all of my code so that I could keep a more informative string in the "track" column in my gat-run output. However, when I got to gat-compare I no longer got any results. Inspecting the code it seems that the things around lines 264-270 of gat-compare, the code assumes that the "track" column only contains the string "merged". This would be the case when using --ignore-segment-tracks as I was doing previously, but now with my more "informative" track strings, this blocks things.

Would it be possible to add to the code so that - similar to what is done in the in-file-comparison part - the list of track values is established and iterated over, to remove this hard-coded limitation?

Thank you in advance for your help!

Best regards,

-- Alex

@AndreasHeger
Copy link
Owner

@skiaphrene , thanks, add this to the next version.

@AndreasHeger AndreasHeger self-assigned this Sep 26, 2016
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

No branches or pull requests

2 participants