Closed tomas-pluskal closed 5 years ago
I can confirm this as a bug. Working on a resolution.
Thanks, Nils! Let me know if I can help.
I added your code as a test case, that is currently all I need, thanks! The culprit is that the implementation has a two-digit order attribute. Everything beyond 99 rolls to 100 and is then treated as 10, which is already assigned to a different column.
Fixed in #12
Hi, it seems jmztab fails to add columns above certain column count. This code demonstrates the issue:
Using jmzTab 3.0.7, this produces the following output:
Note that at count: 27, the columns get messed up (opt_assay[27]_peak_height gets placed after taxid) and no further columns are added to the end.