Skip to content

Conversation

@lmoneta
Copy link
Member

@lmoneta lmoneta commented Jan 13, 2026

This PR superseeds #19692 fixing the conflicts and add some bug fixes

@guitargeek
Copy link
Contributor

Thanks for the PR! One two things to do before a more detailed review is to merge #15790 and fix the test failures in this PR. But I also have a general question, the same as in #19692 (comment): why not remove the old C++ parser at the same time, so we don't risk code duplication and user confusion?

@github-actions
Copy link

Test Results

    23 files      23 suites   3d 18h 49m 8s ⏱️
 3 817 tests  3 815 ✅ 0 💤  2 ❌
80 402 runs  80 385 ✅ 0 💤 17 ❌

For more details on these failures, see this check.

Results for commit 8f68647.

PrasannaKasar and others added 8 commits January 14, 2026 11:33
…ers and added tests for them. Imported Keras within the required functions. Created new CMakeLists.txt file for the keras parser. Made changes in the pythonization CMake file to build the keras parser files
…aced import keras_version with get_keras_version and called it in necessary files
… directory. Used import numpy statements within the parser functions to avoid slowing down the import of ROOT.
… Keras3 Sequential

In Keras3 Sequential output of a layer can have a different name than input of the next layer.
Since in sequnrial model each layer has a single input/output use as output names the layer name (which is unique) and set as input name for the next layer
@lmoneta lmoneta force-pushed the tmva_sofie_keras_parser_prasanna branch from 8f68647 to 7d939fe Compare January 14, 2026 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants