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

Generality vs Complexity #214

Open
r-pascua opened this issue Feb 21, 2022 · 0 comments
Open

Generality vs Complexity #214

r-pascua opened this issue Feb 21, 2022 · 0 comments
Milestone

Comments

@r-pascua
Copy link
Contributor

r-pascua commented Feb 21, 2022

I'm creating this issue because of a short discussion in #212 regarding the current state of hera_sim perhaps being too complex. I know that for my current and planned uses, I like the amount of generality and extensibility afforded by the current implementation, but I don't know what the community thinks, and I'm well aware that the level of complexity makes for a steep learning curve to developing, and this is particularly true when it comes to the Simulator class. @steven-murray and I had discussed this quite a bit in the past, but I don't think we were able to figure out a resolution that maintains the level of generality and extensibility in a simpler implementation. If there is a desire to see changes to the current implementation, then we will revisit this and try to find a solution before the next major version release.

So, I would like people who use (or plan to use) hera_sim (and in particular the systematics simulation stuff) to leave their thoughts here. Is the current state of the code too hard to parse? Is it easy or difficult to use the features it provides? Are the (up-to-date) tutorials thorough enough for getting spun up on how to use the code, or do they need to be improved? Are there other concerns you'd like to discuss that aren't covered by the other prompts? Please let us know.

It looks like much of the previous discussion of this must have happened via Slack, since I can't find an issue or PR where we discussed this. That said, we did have some back-and-forth on an improved implementation of the defaults-switching feature in #135 that does touch on this to some extent.

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

1 participant