LOVD 2.0

Welcome to the LOVD 2.0 bug tracking system. Please note that this bug tracking system is not for LOVD 3.0!

If you have any issues, please read the documentation and Frequently Asked Questions.
Please note that you need to register before you can submit bugs or feature requests.

Information By default, all closed tasks are hidden from view.
Click here to see all tasks.


FS#16 - Error in creating sorting code with variants starting with \"c.(\".

Attached to Project: LOVD 2.0
Opened by Ivo F.A.C. Fokkema (ifokkema) - Thursday, 06 September 2007, 14:56 GMT+1
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Thursday, 06 September 2007, 16:14 GMT+1
Task Type Bug Report
Category Backend / Core
Status Closed
Assigned To Ivo F.A.C. Fokkema (ifokkema)
Operating System All
Severity Medium
Priority High
Reported Version 2.0-beta-07
Due in Version 2.0-beta-08
Due Date 2007-09-07
Percent Complete 100%
Votes 0
Private No


Variants starting with \"c.(\" do not sort correctly. For instance, consider the following sorting order:


The variant \"c.(389G>C?)\" should sort in between the other two.
This task depends upon

Closed by  Ivo F.A.C. Fokkema (ifokkema)
Wednesday, 12 September 2007, 10:09 GMT+1
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 2.0-beta-08, released 2007-09-07.
Comment by Ivo F.A.C. Fokkema (ifokkema) - Thursday, 06 September 2007, 16:14 GMT+1
Due to an error in the lovd_sort() function, variants starting with \"c.\" or \"g.\" or \"(\" were correctly interpreted, but variants with \"c.(\" where not. Due to the lack of a proper sorting code, those variants were sorted as the first variants of their respective exons.