Hi @egraveri ,
as you might remember the predictions of the Hamburg model we recently produced stop around May 2017.
The reason for this is that the file data/temperature/temperature.root contains the temperatures for most of the TT boxes only up to this date.
Since this root file is produced using the script /macros/runCond/tempExtract.C I thought this information could be missing from its input file: /data/temperature/tttemp.txt.
This was originally the case but, after Preema redumped the temperatures around the 6th of November, everything is now up to date in this file.
After checking things around I am pretty sure I found the lines where the new temperatures get discarded. Here I attach a listing of these lines (around L.225 of /macros/runCond/tempExtract.C):
std::vector<double>::iterator it=v_time.begin();
for (std::vector<double>::iterator j=v_temp.begin(); j!=v_temp.end(); it++, j++) {
if (getStdev(v_temp,(int)(j-v_temp.begin()),10)<20.0 && TMath::Abs(*j-getMean(v_temp,(int)(j-v_temp.begin()),10))>2.5) {
v_time.erase(it);
v_temp.erase(j);
it--;
j--;
}
}
getMean, to my understanding, returns the average of the measured temperatures in the interval of measurements [j-10, j+10], where j is the measurement of interest.
This selection does not seem to rise for a necessity, like throwing away bad data, but more likely to reduce the number of points in the plots and even out the oscillation of the temperature evolution.
I think that since the temperatures might have oscillated a little faster recently this selection keeps getting rid of all the last temperatures for the TT.
Notice that this works perfectly for the IT.
I tried to see how the plots change modifying the >2.5 condition. They can be found in /home/hep/matzeni/STAging/macros/runCond/.
Here you can see the plot for TT as Christian was doing. TT_temp_evo_CHEon.pdf
Hi @egraveri ,
as you might remember the predictions of the Hamburg model we recently produced stop around May 2017.
The reason for this is that the file
data/temperature/temperature.root
contains the temperatures for most of the TT boxes only up to this date.Since this root file is produced using the script
/macros/runCond/tempExtract.C
I thought this information could be missing from its input file:/data/temperature/tttemp.txt
.This was originally the case but, after Preema redumped the temperatures around the 6th of November, everything is now up to date in this file.
After checking things around I am pretty sure I found the lines where the new temperatures get discarded. Here I attach a listing of these lines (around
L.225
of/macros/runCond/tempExtract.C
):getMean
, to my understanding, returns the average of the measured temperatures in the interval of measurements [j-10, j+10], where j is the measurement of interest.This selection does not seem to rise for a necessity, like throwing away bad data, but more likely to reduce the number of points in the plots and even out the oscillation of the temperature evolution.
I think that since the temperatures might have oscillated a little faster recently this selection keeps getting rid of all the last temperatures for the TT.
Notice that this works perfectly for the IT.
I tried to see how the plots change modifying the
>2.5
condition. They can be found in/home/hep/matzeni/STAging/macros/runCond/
.Here you can see the plot for TT as Christian was doing.
TT_temp_evo_CHEon.pdf
Here is what we obtain if we uese
2.7
insetead of2.5
:TT_temp_evo_CHEon27TT.pdf
Here when we use
3
:TT_temp_evo_CHEon3TT.pdf
And here when we ignore this condition:
TT_temp_evo_CHEoff.pdf
Since I am not sure of what we should do I wanted to ask for your opinion!
Let me know!
Cheers