epoyraz / mztab

Automatically exported from code.google.com/p/mztab
0 stars 0 forks source link

Bugs in jmzTab related with ms_run-location #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. ms_run[1]-location in the specification allow null values but the jmzTab 
library fail the testing process.
2. The Unknown modifications should be implemented in jmztab using CHEMOD 
notation for converters.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by ypriverol on 15 Sep 2014 at 3:48

GoogleCodeExporter commented 9 years ago
The issue related with CHEMOD will be tracked in issue 16.

Original comment by noedelta on 7 Oct 2014 at 3:04

GoogleCodeExporter commented 9 years ago
This issue was updated by revision r583.

The errors reported previously in the parser have been transformed as warnings. 
Previously the parser stopped if an error was found in the metadata. As the 
warnings are stored internally in the same error list than the errors 
(something to improve in the future) the behaviour of the parser has been 
changed and it will not stop if an error or a warning it is found in the 
metadata section, it will try to continue parsing the rest of the document.

Original comment by noedelta on 8 Oct 2014 at 10:56