Fix spurious PV warning in JetTagDQA

The JetTagDQA was reporting spurious warning due to

if (m_PV_x != -999.) ATH_MSG_WARNING( ".... second PV in the events ...!!!!!!");

because m_PV_x was keeping the value from the previous event.

Fixed by making the PV variable local to the execute function rather than class members.

Merge request reports

Loading