Skip to content
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

Issues with nnlojet runcard autogeneration #73

Open
4 tasks
scarlehoff opened this issue Apr 12, 2024 · 5 comments
Open
4 tasks

Issues with nnlojet runcard autogeneration #73

scarlehoff opened this issue Apr 12, 2024 · 5 comments
Assignees

Comments

@scarlehoff
Copy link
Member

  • At the moment all the WP / WM datasets are split into a WP and WM runcard. This should only be done if there's only one observable in the set, otherwise assume that the WP and WM channels are separated.
  • Update the conda package to include the nnlojet python package
  • Add multi-histogram option (this is needed for more complicated cuts)
  • Automatize a bit more the options-per-experiment.

Please comment with other problems you find.

@achiefa
Copy link

achiefa commented Apr 13, 2024

HI @scarlehoff, I've just realised that the warmup for the VV channel didn't go through. In particular, I get a segmentation fault at the first iteration, as shown below

 ------------------------------------------------
 loadNextContrib_chan: loaded VV ...
 warmup...
  > > Entering legacy wrapper for NNLOJET with Vegas! < <
 Entering New Vegas
  $ OMP active
  $ Maximum number of threads:            2
  $ Number of threads selected:            2
Commencing iteration n 1
Number of events: 5000000
Segmentation fault (core dumped)

Note that for all the other channels I was able to complete the warmup. I've also tried to use a different dataset, but nonetheless I come across the same problem with the VV channel.

@scarlehoff
Copy link
Member Author

That's strange (since all the other channels are running).
Can you send me a runcard?

(do you see the same problem if you run locally in the node?)

export OMP_NUM_THREADS=1
export OMP_STACKSIZE=1000M

Just in case this is the VV using slightly more memory per thread.

@achiefa
Copy link

achiefa commented Apr 14, 2024

I tried to run it locally in the node exporting the two env variables and I didn't get the same problem. I think this solves the problem.

@scarlehoff
Copy link
Member Author

Try only with the second one. If that solves the problem then I'd recommend you use it always (you probably were close to the limit in the others they just happened to work).

If you also need the threads=1 that means there's something wrong with the installation, because I can run the VV multithreaded

@achiefa
Copy link

achiefa commented Apr 14, 2024

Yes, I'm using only the second one and it works. Many thanks @scarlehoff !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants