-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RF] RooFit workspace work differently with pyROOT in 6.32-rc1 version and 6.30/02 #15479
Comments
Hi @yuhao-wang-nju, thanks for your post!
Thanks a lot! Related PR: #14237 |
Hi @guitargeek , thanks a lot for the reply and sorry for the late message. For the first and second point, thanks a lot for the explanation. I may misunderstood the way cppyy works previously, now it seems quite reasonable to me! For the third one, I prepared a workspace and also attached the code that we use (The dataset named The file is a bit large so here is the gdrive link. Thanks a lot in advance for your time! |
After the official release, we tested and found there is no slowdown of the fit. Thanks a lot for the updates and reply! I think we can close the issue now;) |
Thanks for reporting and retesting. |
Check duplicate issues.
Description
Hi root team,
We are the ATLAS VHbbcc analysis team and we are testing with the new root preview version v6.32-rc1 since it has the bug fix related to the issue: https://root-forum.cern.ch/t/cling-jit-session-error-cannot-allocate-memory/56744
However we met some different behavior in this version compared to the previous 6.32/02 that we use.
cppyy.gbl.std.string
object, previously it is a pythonstr
object. May I ask it is designed or a bug?re.findall()
function. But according to the cppyy document, the cppyy should convertcppyy.gbl.std.string
tostr
automatically when thestr
is needed. So what is the reason for not being converted automatically?Thanks a lot for your time
Yuhao
Reproducer
ROOT version
6.32-rc1
Installation method
build from source
Operating system
Linux el9
Additional context
No response
The text was updated successfully, but these errors were encountered: