Closed caredg closed 3 years ago
@caredg See PR #45 for a fix. Something about the continue statement (rather than an if) was messing up the indexing of btags, and this particular event seems to have gotten more btag values in that vector than there were jets....I was able to run the whole file with this fix.
fixed with 65bf99b
@jmhogan, I made a larger scale test executing the poet_cfg.py over all events (-1). I tested this with
isData=True
anddoPat=False
, with the JSON quality activated, and using local (new 2012 directory in container) and remote access to the DB. In both tests, the job fails with the seg violation below [1]. There is a core dump, which I could't learn much from usinggdb
, unfortunately.A similar test but with
isData=False
anddoPat=False
finishes fine. A similar test but withisData=True
anddoPat=True
goes fine as well. A similar test but withisData=False
anddoPat=True
goes fine too.If I repeat the first test, the one that fails, but excluding the myjets process, the job runs fine.
Just to confirm there is no issues with exhausting my machine's memory, I tried the first test in one of the lxplus machines with the singularity container and the result is the same. This time however, the core dump is expanded (not sure if it is useful) [2]
[1]
[2]