Has anyone witnessed the time stamp problem in Masshunter Quant?
If you are open a batch and add files from acquiring data, the time stamp recorded is 03/20/2018 3:30 PM.
The time stamp is retained unless the file in question is removed and added again once the acquisition completes.
At that point it reflects the correct data and time.
I don't see it as a flaw, and it can be prevented by procedure (not processing acquiring data).
But some users are questioning whether it is a noted software bug and Agilent has seen it.
It is present in both versions of software we are currently using.