root [16] R->Scan("helicity:pairsynch:multipletsynch:oversample","") ************************************************************ * Row * helicity * pairsynch * multiplet * oversampl * ************************************************************ * 0 * 1 * 1 * 0 * 771 * * 1 * 1 * 1 * 0 * 3 * * 2 * 1 * 1 * 0 * 259 * * 3 * 1 * 1 * 0 * 515 * * 4 * 1 * 1 * 0 * 771 * * 5 * 1 * 1 * 0 * 3 * * 6 * 1 * 1 * 0 * 259 * * 7 * 1 * 1 * 0 * 515 * * 8 * 1 * 1 * 0 * 771 * * 9 * 1 * 1 * 0 * 3 * * 10 * 1 * 1 * 0 * 259 * * 11 * 1 * 1 * 0 * 515 *
(Helicity should be something like 1(4x), 0(4x), 0(4x), 1(4x)...; pairsynch should be 1(4x), 0(4x), 1(4x), 0(4x)...; multipletsynch should be 1(4x), 0(12x)...; and oversample should be 1, 2, 3, 4, 1, 2, 3, 4...)
My guess is either there is something wrong with these signals, or with what the database says about finding those signals.
There also are many other error messages presumably due to problems with the database and/or the devices list:
WARNING: Header for VQWK was zero. Using default ffadd000 WARNING: Mask for Vqwk was zero. Using default fffff000 WARNING: Header for PVDIS Scaler was zero. Using default ff380100 WARNING: Mask for PVDIS Scaler was zero. Using default ffffffff TaDevice::GetKey:: ERROR: cannot find key batt3r returning zero TaDevice::AddRawKey::WARNING: Key batt3r not in the pre-approved list. TaDevice::GetKey:: ERROR: cannot find key batt4r returning zero TaDevice::AddRawKey::WARNING: Key batt4r not in the pre-approved list. TaDevice::GetKey:: ERROR: cannot find key batt5r returning zero TaDevice::AddRawKey::WARNING: Key batt5r not in the pre-approved list. ... TaDevice::GetKey:: ERROR: cannot find key batt3r returning zero TaDevice::GetKey:: ERROR: cannot find key batt4r returning zero TaDevice::GetKey:: ERROR: cannot find key batt5r returning zero ...
A copy of this log entry has been emailed to: rom@jlab.org,kkumar@jlab.org,paschke@jlab.org