L0 App ReplayL0DUOnly

Add ReplayL0DUOnly option to recompute L0DU decision using the existing L0Calo and L0Muon data (Pending update used by Olli in 2015, now needed by Sascha - @sstahl)

Validation started with lhcb-2016-patches#26

Validation started with lhcb-2016-patches#27

If this is used in the nightlies, wouldn't it affect all tests as it changes some files which are used in the tests?

Yes, that's the point of the nightlies, no? However, as far as I can see, the default behaviour has not change so no influence on the tests is expected

@cogan, I merged changes from master to 2016-patches, so now this MR includes only your change. No action needed from you.

By the way, L0Conf looks a better place for this type of change as all the logic is there and not in L0App. But let's not delay that feature.

Yeah, that is the point of the nightlies. I was only realising that basing on the wrong branch will be another way to screw the nightlies.

Yep, we need another layer of tests: https://its.cern.ch/jira/browse/LBCORE-1114 I know what has to be done I think. Let's see when I get to this.

Status changed to closed

Status changed to reopened

Validation started with lhcb-2016-patches#28

Validation started with lhcb-2016-patches#29

Status changed to merged

mentioned in commit f21ed9b5

Mentioned in commit f21ed9b5