|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
 |
|
|
Message ID: 3060
Entry time: 19 Jun 2025
In reply to: 3054
|
Author: |
Stefan Ritt |
Topic: |
Bug Report |
Subject: |
History variables with leading spaces |
|
|
I added now code to the logger so it properly complains if there would be a leading space in a variable name.
Stefan
> By accident we had history variables with leading spaces. The history schema check then decides that this is a new variable (the leading space is not read from the history file) and starts a new file. We found this because the run start became slow due to the many, many history files created. It would be nice to just get an error if one has a malformed variable name like this.
>
> How to reproduce: Try to put a variable with a leading space in the name into the history, repeatedly start runs.
> Sugested fix: Produce an error if a history variable has a leading space. |