Fix RUN_SEQ_NUMBER

[jhakala]

These logs indicate that the various level2s are not getting a consistent RUN_SEQ_NUMBER:

INFO [HCAL LVL2 HCAL_HBHEb] Executing startAction
2017-06-02 19:44:07 and 293 ms : cms.hcalpro.rcms.fm.app.level1.HCALEventHandler
INFO [HCAL HCAL_HBHEa ] Received and set RUN_NUMBER from last input= Start. Here is the set value: 295934
2017-06-02 19:44:07 and 293 ms : cms.hcalpro.rcms.fm.app.level1.HCALlevelTwoEventHandler
INFO [HCAL LVL2 HCAL_HBHEc] Executing startAction
2017-06-02 19:44:07 and 293 ms : cms.hcalpro.rcms.fm.app.level1.HCALEventHandler
INFO [HCAL HCAL_HBHEa ] Received and set RUN_SEQ_NUMBER from last input= Start. Here is the set value: 0
2017-06-02 19:44:07 and 293 ms : cms.hcalpro.rcms.fm.app.level1.HCALEventHandler
INFO [HCAL HCAL_HBHEb ] Received and set RUN_NUMBER from last input= Start. Here is the set value: 295934
2017-06-02 19:44:07 and 293 ms : cms.hcalpro.rcms.fm.app.level1.HCALEventHandler
INFO [HCAL HCAL_HBHEc ] Received and set RUN_NUMBER from last input= Start. Here is the set value: 295934
2017-06-02 19:44:07 and 293 ms : cms.hcalpro.rcms.fm.app.level1.HCALEventHandler
INFO [HCAL HCAL_HBHEb ] Received and set RUN_SEQ_NUMBER from last input= Start. Here is the set value: 0
2017-06-02 19:44:07 and 293 ms : cms.hcalpro.rcms.fm.app.level1.HCALEventHandler
INFO [HCAL HCAL_HBHEc ] Received and set RUN_SEQ_NUMBER from last input= Start. Here is the set value: 0

[kakwok]

Can this be closed now? @jhakala

[kakwok]

Update: RUN_SEQ_NUMBER is consistent across LV2s and as the log showed, they are correctly obtained from LV1. The real issue here is why LV1 gets 0 as RUN_SEQ_NUMBER. Documentation about RUN_SEQ_NUMBER is here

https://twiki.cern.ch/twiki/bin/view/CMS/RunInfo