[tmva][sofie] Disentangle PyMVA and SOFIE

[guitargeek]

So far, the part of SOFIE that uses the C Python API was included in PyMVA for convenience, but the functionality is completely unrelated.

Moving this code to SOFIE itself means we can fully build and test SOFIE without enabling tmva-pymva.

The only subtelty is that we want to be able to disable these SOFIE features that require linking against libpython, because this is not always allowed (e.g. in the Python wheels). Therefore, this part is only built if we build also the other ROOT libraries that links against libpython besides PyMVA, wich is TPython.

[github-actions]

Test Results

    22 files      22 suites   3d 17h 23m 46s ⏱️
 3 779 tests  3 778 ✅ 0 💤 1 ❌
81 204 runs  81 203 ✅ 0 💤 1 ❌

For more details on these failures, see this check.

Results for commit 5b3842b.

♻️ This comment has been updated with latest results.

[lmoneta]

Thank you Jonas for moving the Keras and PyTorch aprser away from PyMVA. A comment I have it is maybe to be more consistent, is to move them not in sofie but in the sofie_parsers.
Something to discuss

[guitargeek]

Thank you Jonas for moving the Keras and PyTorch aprser away from PyMVA. A comment I have it is maybe to be more consistent, is to move them not in sofie but in the sofie_parsers. Something to discuss

Sure, this can be done! I agree it's better to move it into sofie_parsers.

[guitargeek]

Hi @lmoneta, I have implemented your suggestion to moving the parser implementation to tmva/sofie_parses as you suggested. That means it's now conditional on the tmva-sofie=ON build flag, just like the ONNX parser.

I left the tests in tmva/sofie/test though, because also the tests for the ONNX parser is there for now (there is no tmva/sofie_parsers/test directory)