feat(BSS2): Add and enable jaxsnn
This adds jaxsnn to the ESD.
(Just testing for now…)
Merge request reports
Activity
added 2 commits
mentioned in merge request !498 (merged)
added 2 commits
maybe check the test results, as in !498 (merged)? They don't look great
Test Summary: Errors...: 19 Failures.: 0 Skipped..: 0 Total....: 19
I'm a bit hesitant to "layer" changes on top of each other in MRs… (in my usual gerrit workflow I use it all the time, because changes might depend on other changes) — if a merge happens → ugly history with duplicated commits (even if it's a noop on the repo state); if it's a rebase, it's still weird to do so w/ gitlab. It just feels "hacky" to use it that way.
I meant I'm just not sure why the changes in this MR depend on the changes in !498 (merged)? (or you meant the other way round?)
added 6 commits
-
897fd74f...93c18642 - 2 commits from branch
master
- 5491e4af - feat(jax): add new versions
- efcaa5e0 - feat: add py-optax
- 10b055b7 - feat(BSS2): add jaxsnn (event-based ML)
- 7d291b22 - feat(BSS2): enable jaxsnn
Toggle commit list-
897fd74f...93c18642 - 2 commits from branch
added 2 commits
added 2 commits
added 2 commits
added 2 commits
added 2 commits
added 6 commits
-
783a108d...407893ff - 2 commits from branch
master
- be0a42ef - feat(jax): add new versions
- 7295d04d - feat: add py-optax
- 65922878 - feat(BSS2): add jaxsnn (event-based ML)
- 25eb3601 - feat(BSS2): enable jaxsnn
Toggle commit list-
783a108d...407893ff - 2 commits from branch
@emuller looks ok now, should I merge this?
mentioned in merge request !512 (merged)