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

Ensure naming consistency with all networks and losses #6

Open
justusschock opened this issue Jul 16, 2019 · 0 comments
Open

Ensure naming consistency with all networks and losses #6

justusschock opened this issue Jul 16, 2019 · 0 comments
Assignees
Labels
todo Things that must be done

Comments

@justusschock
Copy link
Member

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 ?

@justusschock justusschock self-assigned this Jul 16, 2019
@mibaumgartner mibaumgartner transferred this issue from delira-dev/vision_base Aug 3, 2019
@mibaumgartner mibaumgartner added the todo Things that must be done label Aug 3, 2019
@mibaumgartner mibaumgartner added this to the First Release (0.1.0) milestone Aug 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
todo Things that must be done
Projects
None yet
Development

No branches or pull requests

2 participants