Blackmagic Design LOG inside of Nuke

In this guide I hope I can help to better utilize Blackmagic Designs LOG-formats inside of Nuke.
For this to work, we need a custom OCIOconfig. All default colourspaces will be maintained as well.

Download the custom config.ocio: https://lucloud.fuke.it/index.php/s/ctCMLzLD3PLWeNj

Copy this config.ocio file anywhere on your computer or server; a good default-location could be
/.nuke/OCIOConfigs/configs/your_config_name

This OCIOConfig was send to me by Peter from Foundrys support, and he kindly allowed it to share. However what I can not and will not share are the LUTs this config is referencing.
To work, you need Nukes default .spi1d LUTs as well as Resolves BMDFilm to Linear .cube LUTs.
The latter come with any install of DaVinci Resolve which can be obtained free from their Website, the path on your computer is as follows:
MacOS: /Library/Application Support/Blackmagic Design/DaVinci Resolve/LUT/VFX IO/
Windows C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\LUT\VFX IO\
(I have no idea where this will be on Linux, sorry)
Note that only three LUTs are available. I don't know which and if they are suitable for the Pocket 4K, Pocket 6K and Ursa 12K cameras; when in doubt, you can probably use a Colorspace Transform effect to choose the proper conversion to linear and export a LUT from that.

For the NUKE LUTs, you can find them in your install directory. For MacOS, you have to right click the basic Nuke.app (not X or Studio!), "show package contents", and then navigate to
/Contents/Resources/OCIOConfigs/configs/nuke-default/luts
On Windows, it's an equivalent to this path. On Linux, again, no idea.

When all those LUTs are recovered, they need to go into /.nuke/OCIOConfigs/configs/your_config_name/luts/
Open up config.ocio in a texteditor and make sure that all LUTs are properly referenced, in case that Blackmagic Design or Foundry renamed them or added some in the in the meantime.

The setup within Nuke is fairly easy. First we have to hop into the Preferences, and under Project Defaults->Color Management we set the drop-down menu to custom and navigate to our config.ocio
This takes care of our script-defaults. In running scripts, we need to enter the Project Settings (hotkey S within the nodegraph). Switch to the color-tab, set the color management to OCIO, OCIO config to custom and the custom OCIO config should direct, once again, to our custom.ocio

When setup like this, we can now set the colourspaces of our Read and Write nodes accordingly and properly linearize our material.
I modified the ocio.config I received from Peter a bit to register lots of Viewer LUTs that I would potentially utilize. If you don't want all of them, just delete them out of your config.
You can now also manually add any LUT you want to!

A few things to note: when you now want to utilize those LUTs within a script, the normal Colorspace node won't give them to you. You now need to use the OCIO Colorspace node.