Skip to content

Refactoring of EkfacInfluence #606

@schroedk

Description

@schroedk

By now, there is the inheritance TorchInfluenceFunctionModel->EkfacInfluence
and EkfacInfluence is the only existing subclass.

In order to reduce code duplication:

  • Check, if it makes sense to inherit from TorchComposableInfluence
  • If not, integrate functionality from base class TorchInfluenceFunctionModel
    into EkfacInfluence
  • Remove abstract base class TorchInfluenceFunctionModel

Metadata

Metadata

Assignees

Labels

breaking-changeChanges to the APIcleanupwhen code is ugly or unreadable and needs restyling

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions