A common bug which leads to broken txt-output in MaxQuant is a system environment which uses comma , as decimal separator (common in, e.g., german locales).
To get correct results in MaxQuant, the locale needs to be UK/US with a '.' (dot) as decimal separator.
PTXQC should be able to detect txt-folders which were created with a wrong locale and refuse to create a report (because the results are bogus anyway).
Also, it would be nice if the report's html code could check the current locale of the system where the report is shown in the browser. This way, the user has an immediate way of checking if the current system would be able to run MaxQuant.
A common bug which leads to broken txt-output in MaxQuant is a system environment which uses comma
,as decimal separator (common in, e.g., german locales). To get correct results in MaxQuant, the locale needs to be UK/US with a '.' (dot) as decimal separator.PTXQC should be able to detect txt-folders which were created with a wrong locale and refuse to create a report (because the results are bogus anyway). Also, it would be nice if the report's html code could check the current locale of the system where the report is shown in the browser. This way, the user has an immediate way of checking if the current system would be able to run MaxQuant.