Closed andreh12 closed 7 years ago
To change the version of required dependency (e.g. DAQAggregator) the pom.xml needs to be updated:
<dependency>
<groupId>ch.cern</groupId>
<artifactId>DAQAggregator</artifactId>
<version>1.16.0</version>
</dependency>
The built version (artifact) needs to be published to our project repository:
http://dev-daq-expert.cern.ch/artifactory
In pom this repository is configured here:
<repositories>
<repository>
<id>libs-release-local</id>
<url>http://dev-daq-expert.cern.ch/artifactory/libs-release-local</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
@hsakulin proposed to cover the case where no FED has sent corrupted data but RU is in Failed state. The idea would be to create separate LM that identifies it. @mommsen might be helpful with preparing the suggestion. Sample cases:
1) Expert: http://daq-expert.cms/DAQExpert/?start=2017-05-19T13:21:28.712Z&end=2017-05-19T14:23:06.399Z
DAQView: http://daq-expert.cms/daq2view-react/index.html?setup=cdaq&time=2017%2005%2019%2015:28:50
2) Here also backpressure was detected
Expert: http://daq-expert.cms/DAQExpert/?start=2017-06-09T15:08:50.975Z&end=2017-06-09T15:33:36.984Z
DAQView: http://daq-expert.cms/daq2view-react/index.html?setup=cdaq&time=2017%2006%2009%2017:14:42
The case when one or more RUs go to failed state without FEDs sending corrupted data is what is proposed in issue #70. I have some code here https://github.com/andreh12/DAQExpert/blob/feature/ru-failed-logic-module/src/main/java/rcms/utilities/daqexpert/reasoning/logic/failures/RuFailed.java but I have not produced a pull request yet because it was based on the branch merged in this pull request and we need a change to the usefulnesses.
now requiring in FC2 that there is both
(previously FC2 fired even if there was no FED data corruption)
needs cmsdaq/DAQAggregator/pull/90 to compile