Adding ParticleNet files in structure needed for SONIC

[wpmccormack]

This is a companion PR to cms-sw/cmssw#37964. We are adding a SONIC producer for ParticleNet (AK4, AK8 General, Mass Decorrelation, and MassRegression) to CMSSW to do some production tests. Nominally SONIC is designed to enable easy use of co-processors in CMS workflows, but it can also start up CPU-based inference servers within jobs. This PR does not affect any workflow in CMS in any way unless called specifically (the SONIC producer is independent of the generic ParticleNet one). The SONIC framework requires the model files and a specifically formatted config file for the Triton server, and these are contained in this PR in the structure required by NVIDIA Triton. Please refer to these slides for more information about SONIC and our use of NVIDIA Triton: https://indico.cern.ch/event/1143469/contributions/4799423/attachments/2416540/4135308/March_28_JetMET_SONIC.pdf. Note that both ONNX and PyTorch versions of the models are included - SONIC greatly simplifies the running of PyTorch models for CMS

[cmsbuild]

A new Pull Request was created by @wpmccormack (Patrick McCormack) for branch master.

@smuzaffar, @aandvalenzuela, @iarspider, @clacaputo, @cmsbuild, @slava77, @jpata can you please review it and eventually sign? Thanks.
@JyothsnaKomaragiri, @emilbols, @demuller, @andrzejnovak, @AlexDeMoor this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy you are the release manager for this.
cms-bot commands are listed here

[cmsbuild]

Pull request #48 was updated.

[kpedro88]

can you change " particlenet_modelsForSonic" to something more concise, like just "models"?

It's also not clear to me how well the symlink scheme here (which is different from DeepMET) will work with Eras, but I guess right now there isn't an example case of Era usage with ParticleNet.

[cmsbuild]

Pull request #48 was updated.

[wpmccormack]

I changed the directory to "models"

[perrotta]

merge

• Tested together with #37964