ROOT-C++-Python - Benchmarking, comparing, best practices #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ROOT-C++-Python - Benchmarking, comparing, best practices
problem to solve
More and more people see benefits in using ML techniques and in addition to that (or apart from that) they see the benefits from taking advantage of the large data science ecosystem around (scipy, numpy, pandas, matplotlib and many many more) in addition to their ROOT based analyses. But instead of then using these tools there seems to be a high level of caution mainly due to:
desired outcome
The best case scenario would be to come out of this hackathon with a comprehensive but simple presentation (mini-tutorial), that shows best practices on how to integrate non-ROOT-tools in an overall ROOT based analysis, how to transfer data between the ecosystems and which includes some performance comparisons between the different approaches.
So basically a talk that can be used to mitigate the fears of stepping outside of a purely ROOT based analysis and that gives actual starting points on how to do that.
I think that the workload of this project would be threefold:
skills / knowledge needed (for the project, not per person)