CLHEP Random Package -- Problem Tracking ================================================================== BugNumber: 002 Initial Bug Report 5/10/04 ------------------ Version 19.1 Aaron Chou reports serious problems with RandPoissonT and Q when mean is exactly 100. He speculates (correctly) that this has to do with the break point between the table-driven method and the more time consuming (for T) or less accurate in principle (for Q) method used above 100. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Bug Reproduced 5/10/04 -------------- Bug is clear, and is result of improper test for whether the table method can be applied (<= instead of <) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Status of repair ---------------- Repaired 5/10/04. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Problem Rectified 5/11//04 ----------------- version 19.1 ================================================================== BugNumber: 001 Initial Bug Report 1/26/04 ------------------ Version 19.0 Joel Heinrich of CDF reports that under Linux RandEngine generates variates with a mean of .625! - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Bug Reproduced 1/26/04 -------------- Bug is clear, and as Joel says is a result of rand() on Linux giving more than the expected 15 bits. The code in RandEngine was very flimsy, using an | of two shifted (expected 15 bit) numbers to form an answer. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Status of repair ---------------- Repaired same day (mf). Also fixed various documentation links. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Problem Rectified 1/26/04 ----------------- version 19.0 ================================================================== Template for each bug: ================================================================== BugNumber: BugName Initial Bug Report ------------------ Version x.y * * * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Bug Reproduced -------------- circumstances * * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Repair Plans ------------ * * (or technical problems) * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Status of repair ---------------- * * * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Status of repair ---------------- * * (in long-running problems might need more than one) * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Problem Rectified ----------------- version x.z - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Ongoing Caveats --------------- * * * ==================================================================