[QC-427] Fix time stored in trends generated by TrendingTask (#495)

knopers8 · web-flow · commit 3ea98a259455 · 2020-09-29T14:11:46.000+02:00
The move to database timestamps destroyed the plots with time on x axis, this fixes the problem.
diff --git a/Framework/src/TrendingTask.cxx b/Framework/src/TrendingTask.cxx
@@ -83,7 +83,7 @@ void TrendingTask::storeTrend(uint64_t timestamp, repository::DatabaseInterface&
 
 void TrendingTask::trendValues(uint64_t timestamp, repository::DatabaseInterface& qcdb)
 {
-  mTime = timestamp;
+  mTime = timestamp / 1000; // ROOT expects seconds since epoch
   // todo get run number when it is available. consider putting it inside monitor object's metadata (this might be not
   //  enough if we trend across runs).
   mMetaData.runNumber = -1;

Original file line number	Diff line number	Diff line change
`@@ -83,7 +83,7 @@ void TrendingTask::storeTrend(uint64_t timestamp, repository::DatabaseInterface&`
`83`	`83`
`84`	`84`	`void TrendingTask::trendValues(uint64_t timestamp, repository::DatabaseInterface& qcdb)`
`85`	`85`	`{`
`86`		`- mTime = timestamp;`
	`86`	`+ mTime = timestamp / 1000; // ROOT expects seconds since epoch`
`87`	`87`	`// todo get run number when it is available. consider putting it inside monitor object's metadata (this might be not`
`88`	`88`	`// enough if we trend across runs).`
`89`	`89`	`mMetaData.runNumber = -1;`