New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test of tensorflow AOT #23146
test of tensorflow AOT #23146
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-23146/4562 |
A new Pull Request was created by @VinInn (Vincenzo Innocente) for master. It involves the following packages: PhysicsTools/TensorFlow @perrotta, @monttj, @cmsbuild, @slava77, @gpetruc, @arizzi can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild , please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@smuzaffar @VinInn in the preliminary discussion about TF DNN in AOT format it was stated that the basic data files should go into a cms-data package, as usual. In the present PR though we are having just small input files for test. They can be an exception in this respect. |
@fabiocos , yes this small binary file within cmssw is to make sure that scram rule for DNN is working correctly. |
+1 |
merge |
testing the new SCRAM feature to generate AOT code given a model and config.
Not obvious to me where the .pb and config files should eventually be located
(they need to be shared at least by src/plugin and test directory in a package.)
In general there is no need to expose further the generated AOT as it is expected to be encapsulated in an algorithm or module
file and example copied from tensorflow/compile/aot/tests itself