PeptideMapper's result size varies from run to run with multiple threads

[cbielow]

Hi,

this is not necessarily a bug, but somewhat surprising nonetheless:

invoking PeptideMapper without the -c option (which will use all CPU cores of the system) results in different output sizes.
This is caused by line duplications in the result file (which can be resolved easily, but is confusing at first).

Using -c 1 as argument always yields the same results (still with some duplicates for some reason).

Just putting it out there, so people are aware.
Or maybe there is a possibility to make the results unique with internal postprocessing?

[mvaudel]

Thanks for reporting this issue. It should be corrected in the latest release, can you give it a try?