 |
 |
Hello, > > 2) I guess these are mainly dataserver errors > > KanEventInput::KanEventInput.cc(661):Opening collection > > /store/SPskims/R12/14.4.2b/BSemiExcl/00/001235/200110/BSemiExcl_001235_0438 > > Warning: environment variable ROOTSYS is not set. Standard include files > > ignored > > Error: cannot open /MAKEINFO > > !!! There are examples of MAKEINFO files under /platform/ !!! > > Please refer to these examples and create for your platform > > Error: cannot open /MAKEINFO > > !!! There are examples of MAKEINFO files under /platform/ !!! > > Please refer to these examples and create for your platform > > Error: cannot open /MAKEINFO > > !!! There are examples of MAKEINFO files under /platform/ !!! > > Please refer to these examples and create for your platform > > Error: cannot open /MAKEINFO > > !!! There are examples of MAKEINFO files under /platform/ !!! > > Please refer to these examples and create for your platform > > Info in <XTNetFile::CTOR>: (C) 2004 SLAC XTNetFile (eXtended TNetFile) > > V00-00-37-01 I get the messages above appear as well when trying KanCollUtil 'collname', but it does returns the # events and 'physical' filenames corresponding to the given collection, so I think it's ok: /store/SPskims/R12/14.4.2b/BSemiExcl/00/001235/200110/BSemiExcl_001235_0438 (152818 events) > > 040608 15:20:00 713 Err : TXSocket::RecvRaw - Request timed > > out 60 seconds reading 4 bytes from socket 20 > > (server[kan006.slac.stanford.edu:1094]) > > 040608 15:20:00 713 Err : XTNetConn::doHandShake - Error reading 4 > > bytes from the server [kan006.slac.stanford.edu:1094]. > > 040608 15:20:00 713 Info: XTNetConn::GetAccessToSrv - HandShake > > failed with server [kan006.slac.stanford.edu:1094]. > > 040608 15:20:00 713 Err : XTNetConn::goToAnotherServer - Error > > handshaking to [kan006.slac.stanford.edu:1094] > > KanEventInput::KanFileReg.cc(322):KanFileReg: read UUID > > a81fee84-b17f-11d8-8660-ba5ad0c89a64 I think these messages are related to dataserver (or xrootd) errors that occured earlier this week. See KanSOS HN. As far as I can tell, they don't appear anymore in jobs I submitted since yesterday. > > KanEventUpdateAllTheRest::KanTreeBase.cc(235):No Branch called Emc > > KanEventUpdateAllTheRest::KanNewScribe.cc(513): cannot find a branchObject > > Emc > > KanEventUpdateAllTheRest::KanTreeBase.cc(235):No Branch called > > Emc_CandListBank > > KanEventUpdateAllTheRest::KanNewScribe.cc(513): cannot find a branchObject > > Emc_CandListBank > > KanEventUpdateAllTheRest::KanTreeBase.cc(235):No Branch called L1Glt > > KanEventUpdateAllTheRest::KanNewScribe.cc(513): cannot find a branchObject > > L1Glt > > KanEventUpdateAllTheRest::KanTreeBase.cc(235):No Branch called > > Reco_EmcCands > > KanEventUpdateAllTheRest::KanNewScribe.cc(513): cannot find a branchObject > > Reco_EmcCands > > KanEventUpdateAllTheRest::KanNewScribe.cc(355): couldn't make a transient > > on read for L1FctSimTimeK > > This is either the first event (probably normal) or whether or not it > > is there is changing from event to event (not expected). > > probably normal if the output is there and you can read it. Did you check > the integrity of the file (for instance by using KanCollUtil)? > Yes, I think this is normal, it only occurs for the first event (as stated in the last sentence of the output). It also occurs for the signal where we produced the skims ourselves. > > 3) The following is printed out for many, many (every?) event > > CompIbuNtpDump::BtaMcAssoc.cc(410):BtaMcAssoc::checkPdtHypo: returns 0 > > because pdtEntry > > or candidate is null. Please check that you have > > valid candidates before calling this method. > > o original candidate pntr: 0x13b9b740 > > o original candidate pdtEntry pntr: 0xff4d0d8 > > o matched candidate pntr: (nil) > > o matched candidate pdtEntry pntr: (nil) > > this seems to be not good. It has to be checked carefully. Do you have it > in all MC jobs? > Yes, this appears in all MC jobs, generic-bb, vub-signal and also the cocktail that Ed submitted. Urs checked that the frequency does not correspond to unmatched tracks or clusters. Any ideas? Cheers, Henning