Netx

[bamsumit]

Issue Number: 29

Objective of pull request:
NetX implementation

Pull request checklist

Your PR fulfills the following requirements:

• Issue created that explains the change and why it's needed
• Tests are part of the PR (for bug fixes / features)
• Docs reviewed and added / updated if needed (for bug fixes / features)
• PR conforms to Coding Conventions
• PR applys BSD 3-clause or LGPL2.1+ Licenses to all code files
• Lint (pyb) passes locally
• Build tests (pyb -E unit) or (python -m unittest) passes locally

Pull request type

Please check your PR type:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation changes
• Other (please describe):

What is the current behavior?

• Not Implemented

What is the new behavior?

• Automatic generation of Deep networks through NetX api.

Does this introduce a breaking change?

• Yes
• No

Supplemental information

[mgkwill]

This is good work @bamsumit!

Some suggestions on docstrings, comments, TODOs in code.

Generally I don't think we should have comments in released code that is not germane to explaining something. Comments should use standard English grammar.

I.E. I think we should remove all commented code. Also TODOs should be in Github issues and not in the code itself (need to work on Lava for this also).

[bamsumit]

This is good work @bamsumit!

Some suggestions on docstrings, comments, TODOs in code.

Generally I don't think we should have comments in released code that is not germane to explaining something. Comments should use standard English grammar.

I.E. I think we should remove all commented code. Also TODOs should be in Github issues and not in the code itself (need to work on Lava for this also).

Thanks for the comments @mgkwill I have attended to them :)

[mgkwill]

@tim-shea are you ready to approve this?

[tim-shea]

Great submission Sumit!