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

The refSeqOrder is not customisable #919

Closed
liub1993 opened this Issue Aug 25, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@liub1993

liub1993 commented Aug 25, 2017

In some case, the reference sequence name is not ordered in proper way, for example, the human chromosomes, named from
'1', '2', '3', ..., '22', 'X', 'Y', 'MT',
but the browser would order the names like this:
'1', '10', '11', '12', ..., '2', '21', ...
when the configuration is set to order by name, and that's not well read for us.

@dsenalik

This comment has been minimized.

Contributor

dsenalik commented Sep 11, 2017

I am proposing a different way to accomplish this goal in issue #925 by preserving the order from the input FASTA file

@rbuels rbuels added the feature req label Jan 25, 2018

@rbuels rbuels added this to the 1.12.4 milestone Jan 25, 2018

@rbuels rbuels self-assigned this Jan 25, 2018

@rbuels rbuels added the in progress label Jan 25, 2018

@rbuels

This comment has been minimized.

Collaborator

rbuels commented Jan 25, 2018

@rbuels rbuels modified the milestones: 1.12.4, 1.12.5 Feb 2, 2018

@rbuels rbuels closed this in 4cf41b7 Feb 27, 2018

@wafflebot wafflebot bot removed the in progress label Feb 27, 2018

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