Replies: 2 comments
-
|
Hi @vfriese, after some investigation I think the underlying issue is that the MvdDigi branch hits the limit of 1GB which is a hard limit in ROOT due to the usage of 32bit Integers. I the size of the written bytes exactly indicates the problem. The number should be positive but in the example it is negative
If I am not wrong doing some simple calculation the size of the MvdDigi data is more than 3GB 43145913 * 80byte =~ 3.2 GB The problem was also seen by the ALICE experiment. Lets further discuss the issue in the Redmine issue. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I tried to look into The error message by I suggest that the return value of |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
With cbmroot, we recently encountered the error message
The message occurs when the number of objects (or the associated memory) to be filled into the tree branch exceeds some threshold. The run proceeds to the end, and the output ROOT file appears intact and can be opened without error. However, some data are not present there (strangely enough, in this case, the MVD data, on which the error complains, are there, but the STS data are not):
More strangely, when I look at the file with

TBrowser, I can see the all data, including the STS (see attached plot).Question: Has this kind of error been encountered before by somebody? Is a cure within fairroot available? I know that there are some
ROOTmethods concerning the tree I/O, likeTTree::SetCacheSize(), but since we use the ROOT I/O scheme through FairRootManager, we have no direct way to try this out.For more details, see https://redmine.cbm.gsi.de/issues/3785 (needs CBM Redmine Account).
Beta Was this translation helpful? Give feedback.
All reactions