Architecture library won't work for more than one architecture
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
The architectures library is working right now because there's only one architecture. This will actually break for more than one architecture, refer to the implementation in BBHNet for how to fix this. Better yet, just create a dedicated ML4GW/architectures repo that contains architectures for various purposes and this wrapper.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the architecture-library implementation and comparing it with the wrapper in BBHNet's libs/architectures/bbhnet/architectures/wrapper.py. Determine how the current library handles a single architecture and define the changes needed for multiple architectures. Done means the library and wrapper support more than one architecture without breaking existing use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100