Sebastien Binet
Sebastien Binet
once we have write capabilities, we should have `go test` benchmarks: - [ ] write 1 branch with 1 `float64` - [ ] write 10 branches with 1 `float64` -...
it would be great to have some ability to achieve the same things than what ROOT's `HistFactory` or pure-python's `hf` do: - https://github.com/root-project/root/tree/master/roofit/histfactory - https://github.com/diana-hep/pyhf
see: https://github.com/scikit-hep/uproot/issues/54
this would be interesting for Recast. wouldn't it, @lukasheinrich ?
commit 40f83711f2ddda82f19c00cb7f5be5eaf85ebb8f brought the reading of a float64 branch from/to: ``` BenchmarkScanStruct-4 50000 39159 ns/op 801 B/op 100 allocs/op BenchmarkScanStruct-4 200000 10070 ns/op 0 B/op 0 allocs/op ``` ie: ```...
It would be great to implement fast BulkIO access for `rootio`. this can be done in a few lines in python: - https://github.com/scikit-hep/uproot with quite the performances boost: - https://github.com/scikit-hep/uproot#performance...
_From @sbinet on December 7, 2016 16:9_ _Copied from original issue: go-hep/hbook#10_
_From @sbinet on December 7, 2016 16:9_ _Copied from original issue: go-hep/hbook#11_
we might want to consider using `runtime/cgo.Handle` (when released and when gopy's minimum Go version matches Go-1.17) instead of our own mechanism. see: - https://github.com/golang/go/issues/37033 - https://tip.golang.org/pkg/runtime/cgo/#Handle
#222 and #224 were merged to fix #220 and #221. as noted in https://github.com/go-python/gopy/pull/222#issuecomment-604050120, it would be great to add tests for those, to make sure we don't regress at...