file hax/hax/slow_control.py L176.
In the for loop often the variable entry is not a dict type variable. It's expected a kind of ntupla where the entry "timestampseconds" (datetime.utcfromtimestamp(entry['timestampseconds'])) is supposed to be present but very often this is not true.
I don't understand the reasons (some errors in the sc database entries?) I fix this problem by insert in the for loop a check on the entry variable type:
if not isinstance(entry,dict):
continue
This fix the problem, but it's not the only one.
Several time when I try to process the dataset with pax_v6.5.0, cax by means of this hax function try to connect to the slow_control database and only after several attempts (40-50 times) is able to connect and read the Voltage values of each PMT in the AddGains function.
After few tentatives the cax starts to process the run without error messages.
file hax/hax/slow_control.py L176.
In the
forloop often the variableentryis not adicttype variable. It's expected a kind of ntupla where the entry "timestampseconds" (datetime.utcfromtimestamp(entry['timestampseconds'])) is supposed to be present but very often this is not true.I don't understand the reasons (some errors in the sc database entries?) I fix this problem by insert in the
forloop a check on theentryvariable type:if not isinstance(entry,dict):continueThis fix the problem, but it's not the only one.
Several time when I try to process the dataset with pax_v6.5.0, cax by means of this hax function try to connect to the slow_control database and only after several attempts (40-50 times) is able to connect and read the Voltage values of each PMT in the AddGains function.
After few tentatives the cax starts to process the run without error messages.