Users occasionally edit measurement scripts manually and enter sample position strings with leading or trailing whitespace, for example: " 1CB" or
"1CB ". This is easy to do inadvertently and is often intended for readability rather than representing a different sample position.
Currently, when a position string contains extra whitespace, it is not recognised as a valid sample position. The issue is only detected when the script attempts to move the sample changer. At that point, the command is silently ignored because the requested position is not found in the list of valid positions. The run continues, resulting in fewer samples being measured than expected.
This behaviour is particularly problematic for unattended, overnight measurements, where users may only discover later that part of the sample sequence was skipped.
Users occasionally edit measurement scripts manually and enter sample position strings with leading or trailing whitespace, for example: " 1CB" or
"1CB ". This is easy to do inadvertently and is often intended for readability rather than representing a different sample position.
Currently, when a position string contains extra whitespace, it is not recognised as a valid sample position. The issue is only detected when the script attempts to move the sample changer. At that point, the command is silently ignored because the requested position is not found in the list of valid positions. The run continues, resulting in fewer samples being measured than expected.
This behaviour is particularly problematic for unattended, overnight measurements, where users may only discover later that part of the sample sequence was skipped.