Skip to content

Conversation

@veprbl
Copy link
Member

@veprbl veprbl commented Nov 12, 2025

This is a script provided by Alex for debugging B0 acceptance issue. Currently this is setup to use DVCS process as input, but we could fill phase space other way (e.g. see b0_tracker benchmark).

@veprbl veprbl force-pushed the pr/far_forward_dvcs branch from 22fb0f0 to 3bd1c20 Compare November 12, 2025 19:14
@veprbl veprbl force-pushed the pr/far_forward_dvcs branch from 3bd1c20 to 4e684c9 Compare November 12, 2025 19:15
@veprbl veprbl force-pushed the pr/far_forward_dvcs branch from 4e684c9 to 000881c Compare November 12, 2025 19:18
@veprbl veprbl requested a review from ajentsch November 12, 2025 21:18
@veprbl
Copy link
Member Author

veprbl commented Nov 12, 2025

@veprbl veprbl merged commit 374bcda into master Nov 13, 2025
3 checks passed
@veprbl veprbl deleted the pr/far_forward_dvcs branch November 13, 2025 18:20
@simonge
Copy link
Contributor

simonge commented Nov 13, 2025

@ajentsch Would this be more useful as a validation to use 5x41?

@ajentsch
Copy link

For the B0, yes.

@ajentsch
Copy link

So it looks like no B0 tracks were produced in this run.

@veprbl
Copy link
Member Author

veprbl commented Nov 13, 2025

Ah, so this runs 1000 events for test. I usually run 100000 and get 141 tracks when things are working and 18 tracks when things are broken. Do these numbers check out?

We could increase simulated statistics or do a single-particle version of the same benchmark.

@ajentsch
Copy link

I got like 550 B0 tracks for 50000 events in my tests with the June campaign.

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

Successfully merging this pull request may close these issues.

4 participants