Andrew Fitzgibbon
Andrew Fitzgibbon
We used to call the things we benchmarked "tools", now they are "modules". We should unify -- any suggestions welcome.
The "replicate point" option is strange, and might lead to unrealistic timings, e.g. with branch prediction or cache behaviour. We should remove it.
The comment at https://github.com/awf/ADBench/blob/37f7f15137e5c8759785840917e4d773819bfddf/usr/awf/Julia/gmm3.jl#L14 says that the elements in the lower triangle are inserted row-major. This is the sensible order for most of the languages we support, but it appears...
1. make ``cam`` in ``project`` a ``` struct Camera{T} rot :: SVector{3,T} centre :: SVector{2,T} radial :: SVector{2,T} focal :: T X0 : SVector{2,T} ```
Some tools, e.g Eigen, Manual, have multiple "subtools", e.g. *-Split or *-Vector configurations. There is much grotty logic e.g. in run-all: ``` if ($objective.contains("Eigen")) { $out_name = "$($this.name.ToLower())_eigen" } elseif...
Current convention in our C++ files is to begin member variables with an underscore, which is to the letter of the C++ standard, but frowned upon. https://stackoverflow.com/questions/228783/what-are-the-rules-about-using-an-underscore-in-a-c-identifier Workitem: replace ``struct...
Add a breadcrumb for custom ops to performance doc.
It would be great to be able to run e.g. the MNIST example notebook on Paperspace with a "Run on gradient" button.
Was expecting to see doc preview for #23 at https://www.julia-vscode.org/docs/previews/PR23, but it hasn't arrived. Drilling into https://github.com/julia-vscode/docs/pull/23/checks?check_run_id=1044713988 we see errors: ``` 2020-08-29T08:32:55.2884560Z [command]julia --color=yes --project=docs/ docs/make.jl 2020-08-29T08:33:02.7677598Z [ Info: SetupBuildDirectory:...