bad f250 pulse data

[markito3]

Hi,

I have run into a problem with the evio files in run 50924 - hd_root finds a bad f250 pulse and then throws an JException and crashes. Files 000 and 001 crash instantly, file 002 proceeds for 2.1k events and then crashes. I'm using halld_recon version 3.2.0.

Does anyone know which runs do and don't have these errors in them?

Was this already found by the automatic monitoring software? (if not, why not?)

Naomi. aka @nsjarvis

[nsjarvis]

Note that PlotBrowser incoming data is completely blank (not even an empty histogram) for 50924 and a few other runs. That is probably a BIG clue - we should pay more attention to these.

[faustus123]

This was seen back at the time the run was taken. See logbook:

https://logbooks.jlab.org/entry/3608646

The bottom line is, the issue was fixed by a reboot of the crate and the data for the affected runs is unrecoverable.

[faustus123]

I just closed this issue with this comment:

This was seen back at the time the run was taken. See logbook:

https://logbooks.jlab.org/entry/3608646 https://logbooks.jlab.org/entry/3608646 The bottom line is, the issue was fixed by a reboot of the crate and the data for the affected runs is unrecoverable.

Regards, -David

---

David Lawrence Ph.D. Staff Scientist, Thomas Jefferson National Accelerator Facility Newport News, VA davidl@jlab.org (757) 269-5567 W (757) 746-6697 C

On Nov 9, 2018, at 2:47 PM, nsjarvis notifications@github.com wrote:

Note that PlotBrowser incoming data is completely blank (not even an empty histogram) for 50924 and a few other runs. That is probably a BIG clue - we should pay more attention to these.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JeffersonLab_halld-5Frecon_issues_47-23issuecomment-2D437474546&d=DwMCaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=DSufUSddsl3c0GGnbiwkxA&m=Zp8k63oRMX4A92Sz9wOpmCHnHMsWf71QAextbRop6PA&s=Btx_degp-_ImouzEanFen7jdSITV710I8aOjo3kui4E&e=, or mute the thread https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMPm5YqA3NDYxVtxdtJ55-2DFlQbRxbQUwks5utdu3gaJpZM4YXU5O&d=DwMCaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=DSufUSddsl3c0GGnbiwkxA&m=Zp8k63oRMX4A92Sz9wOpmCHnHMsWf71QAextbRop6PA&s=lzjoU9x0UFzogV-0R_9G6QmygAuNmGc13IR8nP5z1wI&e=.

[nsjarvis]

It should be marked as JUNK in RCDB then, please.

On Fri, Nov 9, 2018 at 2:50 PM David Lawrence notifications@github.com wrote:

This was seen back at the time the run was taken. See logbook:

https://logbooks.jlab.org/entry/3608646

The bottom line is, the issue was fixed by a reboot of the crate and the data for the affected runs is unrecoverable.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/JeffersonLab/halld_recon/issues/47#issuecomment-437475771, or mute the thread https://github.com/notifications/unsubscribe-auth/AO7hVtC_1b6-Sw9Cp992xLhQPV0Odu9Oks5utdyfgaJpZM4YXU5O .

[sdobbs]

We usually keep track of this info with the "status" field. It's on my list...

On Fri, Nov 9, 2018 at 2:57 PM nsjarvis notifications@github.com<mailto:notifications@github.com> wrote: It should be marked as JUNK in RCDB then, please.

On Fri, Nov 9, 2018 at 2:50 PM David Lawrence notifications@github.com<mailto:notifications@github.com> wrote:

This was seen back at the time the run was taken. See logbook:

https://logbooks.jlab.org/entry/3608646

The bottom line is, the issue was fixed by a reboot of the crate and the data for the affected runs is unrecoverable.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/JeffersonLab/halld_recon/issues/47#issuecomment-437475771, or mute the thread https://github.com/notifications/unsubscribe-auth/AO7hVtC_1b6-Sw9Cp992xLhQPV0Odu9Oks5utdyfgaJpZM4YXU5O .

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/JeffersonLab/halld_recon/issues/47#issuecomment-437477492, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABIJasg1RDy5KQGqAobpTgt25rztmXNSks5utd4VgaJpZM4YXU5O.

[nsjarvis]

Last time I looked there were no is_production runs for 2018 fall yet, let alone status=approved. Sean's to-do list is too long (and this run period is a real challenge as we have not finished calibrating the previous one yet). Sean, if you want to start up a spreadsheet, I can try to help fill the approved status with the obvious yes/no. At first this is what I thought the spring-2018 monitoring volunteer group was for. :-(

Could we implement a really basic monitoring process to run over a few complete evio files from each run just to check that the data is readable? This should produce an easy yes/no with the minimum of thought required.

Naomi.

On Fri, Nov 9, 2018 at 3:36 PM Sean Dobbs notifications@github.com wrote:

We usually keep track of this info with the "status" field. It's on my list...

On Fri, Nov 9, 2018 at 2:57 PM nsjarvis <notifications@github.com<mailto: notifications@github.com>> wrote: It should be marked as JUNK in RCDB then, please.

On Fri, Nov 9, 2018 at 2:50 PM David Lawrence <notifications@github.com mailto:notifications@github.com> wrote:

This was seen back at the time the run was taken. See logbook:

https://logbooks.jlab.org/entry/3608646

The bottom line is, the issue was fixed by a reboot of the crate and the data for the affected runs is unrecoverable.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/JeffersonLab/halld_recon/issues/47#issuecomment-437475771>,

or mute the thread < https://github.com/notifications/unsubscribe-auth/AO7hVtC_1b6-Sw9Cp992xLhQPV0Odu9Oks5utdyfgaJpZM4YXU5O>

.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub< https://github.com/JeffersonLab/halld_recon/issues/47#issuecomment-437477492>, or mute the thread< https://github.com/notifications/unsubscribe-auth/ABIJasg1RDy5KQGqAobpTgt25rztmXNSks5utd4VgaJpZM4YXU5O>.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/JeffersonLab/halld_recon/issues/47#issuecomment-437487726, or mute the thread https://github.com/notifications/unsubscribe-auth/AO7hVsKFQO8bg65IKdtj019JIrdIJ0lUks5utedhgaJpZM4YXU5O .