Skip to content
This repository was archived by the owner on Jun 26, 2021. It is now read-only.
This repository was archived by the owner on Jun 26, 2021. It is now read-only.

Ensure naming consistency with all networks and losses #6

@justusschock

Description

@justusschock

We should take care of the naming consistency.

here is my Proposal:

  • Everything that can be used directly (either a loss or a network with a closure should contain the backends name (for now, we only have PyTorch here, but we have to decide on whether to name it torch (as the backends name while checking for it) or PyTorch).

  • Everything that cannot be used directly must not contain this kind of suffix, but should not be included in any kind of __init__.py to avoid name confusion.

What do you think of this @delira-dev/vision ?

Metadata

Metadata

Assignees

Labels

todoThings that must be done

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions