GitLab

See if using only one thread to build prevents running out of ram on github actions when building windows examples

* Add WebP support to imglab

* Change order in if/else statements for image saving

* Do not put variants that can hold immutable types to vectors

* Enable build on gcc 11

* Add BGR(A) to pixel_traits

* add support for reading webp

* Apply Davis' suggestions and fix formatting

* Fix signed/unsigned warning

* Update decoding paths

* update pixel traits documentation

* Add support for writing WebP images

* Simplify image_saver code

* WIP: add tests, PSNR is low but images look good

* Add lossless compression for quality > 100

* Fix build when WebP support is disabled

* Use C++ stream instead of C-style FILE

* Fix indentation

* Use reinterpret_cast instead of C-style cast

* Improve impl::impl_save_webp signature

* Remove empty line

* Use switch statement and clean up code

* Update Copyright and test libwebp on Linux

* Fix formatting in github workflow

* Fix operator== for bgr_alpha_pixel

* Show where the test fails

* Add libwebp to CI for the remaining Linux workflows

* Use filename consistently

* Improve message with wrong pixel type

* Fix tests for WebP images

* Prevent saving images which are too large and improve error messages

* Use max dimension from WebP header directly

* Update documentation, index and release notes

* Update dlib/image_saver/save_webp_abstract.h
Co-authored-by: Martin T. H. Sandsmark <martin.sandsmark@kde.org>
Co-authored-by: Davis E. King <davis685@gmail.com>

I don't know how I could miss this.

The loss value should reflect the impact of the gamma parameter, as well.

Warnings about unused variables are quenched by simply incrementing the
variables in question. This makes the try_compile() call in CMake
succeed without warnings when checking for C++11 compatibility and using
-Wall.

When propagating the option "-Xclang -fcxx-exceptions" to targets
linking to dlib, the options with quotes are unknown to clang-cl.
Removing the quotes and splitting the arguments into two works fine.

Clang 7 increased the default template-depth to 1024.

When compiling with other compilers than MSVC, error messages about
C++11 support for versions below MSVC version 19.0.24210.0 were printed.
This happens, for example, when using clang-cl installed with the Visual
Studio Installer.

* Add focal gamma to loss_multibinary_log

* update release notes

* Update docs

* escape & in git_logs_as_xml

Notably, set_all_bn_running_stats_window_sizes and fuse_layers.

But also I took the chance to remove the superflous separators and
change the attribute of upsample layers from stride to scale.

* Refactor visitors into their own header

* Update visitor links in term index

* Move documentation from layers_abstract

* Add visitor to draw nets in the DOT language

* Add documentation

Problem: `Error while calling cudnnGetConvolutionForwardWorkspaceSize( context(), descriptor(data), (const cudnnFilterDescriptor_t)filter_handle, (const cudnnConvolutionDescriptor_t)conv_handle, descriptor(dest_desc), (cudnnConvolutionFwdAlgo_t)forward_algo, &forward_workspace_size_in_bytes) in file C:\a\2\s\3rdparty\dlib\dlib\cuda\cudnn_dlibapi.cpp:1029. code: 9, reason: CUDNN_STATUS_NOT_SUPPORTED` (#2532)

Solution: when this happens, select the best algorithms again - but this time bypassing the cache

Problem: Error while calling cudnnGetConvolutionBackwardFilterWorkspaceSize( context(), descriptor(data), descriptor(dest_desc), (const cudnnConvolutionDescriptor_t)conv_handle, (const cudnnFilterDescriptor_t)filter_handle, (cudnnConvolutionBwdFilterAlgo_t)backward_filters_algo, &backward_filters_workspace_size_in_bytes) in file C:\a\1\s\3rdparty\dlib\dlib\cuda\cudnn_dlibapi.cpp:1048. code: 9, reason: CUDNN_STATUS_NOT_SUPPORTED (#2527)

Solution: Do not apply the cuDNN 5.1 workaround if we have cuDNN version greater than or equal to 7

* Fix Barlow Twins loss gradient

* Update reference test accuracy after fix

* Round the empirical cross-correlation matrix

Just a tiny modification that allows the values to actually reach 255 (perfect white).

* Make github actions run the python unit tests

* why don't the pyhton tests run?

* run python tests

* don't run tests twice

* don't run cmake tests twice

* rename the CMake test to C++ since it's testing the C++ part of the library

And the python build uses cmake too, which makes the naming somewhat
confusing

* work around macos

* oops, fix spelling error