gauge configs stored after reversibility check have trajectory nr = '-1'

[kostrzewa]

There seems to be a logic bug which fails to set the trajectory number correctly after the reversibility check. Gauge configs stored after the reversibility check have a '-1' in their metadata.

I have a feeling that we've fixed this at some point when we've added trajectory numbers to return_check.data

In an HMC run using 85e1cb2, I did not observe this behaviour.

@pittlerf I see that you were using 9b5d056 which appears to be a commit from your fork of the BSM branch: https://github.com/pittlerf/tmLQCD/tree/BSMmerge

I will leave this open until we have verified that this is definitely fixed in the etmc/master branch.