Skip to content

Seems like secondary events for NG911 simulations are parametrized randomly #852

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

Open
stiber opened this issue May 16, 2025 · 0 comments
Open
Assignees
Labels
documentation Improvements or additions to documentation NG911 question Further information is requested

Comments

@stiber
Copy link
Contributor

stiber commented May 16, 2025

# The prototypes are selected base of 4 classes (0-3) where:
# class 0 = 40% of events
# class 1 = 50% of events
# class 2 = 9% of events
# class 3 = 1% of events
# Each of this classes has a mean and standard deviation for the radius
# and intensity of the generated secondary process
proto_class = np.random.rand(len(prim_evts))
proto_class[(proto_class >= 0.99)] = 3
proto_class[proto_class < 0.4] = 0
proto_class[(proto_class >= 0.4) & (proto_class < 0.9)] = 1
proto_class[(proto_class >= 0.9) & (proto_class < 0.99)] = 2

I think that the prototypes for secondary event should be chosen based on the primary event type. This should be verified against @jardiamj 's thesis.

@stiber stiber added documentation Improvements or additions to documentation question Further information is requested NG911 labels May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation NG911 question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants