- 27 Apr, 2019 1 commit
-
-
Davis King authored
given an empty list of initial function evaluations.
-
- 26 Apr, 2019 2 commits
-
-
Davis King authored
-
Edoardo Morandi authored
-
- 19 Apr, 2019 1 commit
-
-
Davis King authored
-
- 15 Apr, 2019 2 commits
-
-
-
Davis King authored
-
- 14 Apr, 2019 1 commit
-
-
Davis King authored
-
- 08 Apr, 2019 1 commit
-
-
Juha Reunanen authored
* Semantic-segmentation loss calculation: fix buffer usage on multi-GPU training * Review fix: make the work buffer live longer
-
- 04 Apr, 2019 1 commit
-
-
Davis King authored
-
- 28 Mar, 2019 1 commit
-
-
Facundo Galán authored
-
- 19 Mar, 2019 6 commits
-
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
- 18 Mar, 2019 7 commits
-
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
- 17 Mar, 2019 1 commit
-
-
Davis King authored
-
- 15 Mar, 2019 4 commits
-
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
- 14 Mar, 2019 1 commit
-
-
Davis King authored
-
- 10 Mar, 2019 8 commits
-
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
Davis King authored
-
- 08 Mar, 2019 3 commits
-
-
Davis King authored
Automatically test for NEON instructions when building python extensions and enable them if available. Forgot about --yes USE_NEON_INSTRUCTIONS when removing --yes a moment ago. It's on by default now so now --yes really is unneeded. The dlib policy on this kind of thing going forward is to always have a cmake script that tests if a feature like this is available and to enable it automatically when building python extensions.
-
Davis King authored
Removed --yes option from setup.py since it has long been a noop and its presence just confuses users.
-
Davis King authored
-