Sweat, thanks! Will check it out! I had it actually half-way implemented it myself, but I can abandon that now.
General question remains though. LA plugin and expecially the BasicCPU runtime module feel very closed off and everything is hidden away behind interfaces or private utility functions. Though I can swap out the model used in the python trainer with my own script, and produce an ONNX artefact for NNE, but that defeats a bit the purpose of the LA plugin to architectect models from C++.
If I could wish for something, I’d like to have a “custom” layer, where I can manually specify what’s serialized back and forth, which python module to use for training, and provide an evaluation function for the runtime.