Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add postprocessing (and fix WASM) #65

Merged
merged 4 commits into from
Sep 25, 2024
Merged

feat: Add postprocessing (and fix WASM) #65

merged 4 commits into from
Sep 25, 2024

Conversation

retraigo
Copy link
Collaborator

This PR adds the following two post-processing functions that run only during the predict routine:

  • Step function
  • Sign function (specific case of step where x < 0 ? -1 : 1)

This PR also fixes the wasm backend. The binary example now uses the wasm backend.

@retraigo retraigo changed the title WIP feat: Add postprocessing (and fix WASM) feat: Add postprocessing (and fix WASM) Sep 24, 2024
@retraigo retraigo enabled auto-merge (squash) September 24, 2024 10:22
@retraigo retraigo requested a review from load1n9 September 24, 2024 10:22
Copy link
Member

@load1n9 load1n9 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@retraigo retraigo merged commit a811fd1 into main Sep 25, 2024
3 checks passed
@retraigo retraigo deleted the postprocess branch September 25, 2024 10:15
retraigo added a commit that referenced this pull request Sep 26, 2024
* add postprocessing for sign and step

* fix wasm
load1n9 pushed a commit that referenced this pull request Sep 30, 2024
* add embeddings

* change import

* update flatten backprop

* feat: Add postprocessing (and fix WASM) (#65) (#66)

* add postprocessing for sign and step

* fix wasm

* update flatten

* allow custom mapping

* update matrix types

* add lstm

* try to fix lstm

* allow other activation

* add config for activation

* add GELU

* build wasm

* wasm

* last lstm test attempt
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants