-
-
Notifications
You must be signed in to change notification settings - Fork 7
Insights: mlr-org/mlr3torch
Overview
Could not load contribution data
Please try again later
1 Release published by 1 person
-
v0.2.0 0.2.0
published
Feb 7, 2025
7 Pull requests merged by 1 person
-
feat(learner): initialize shuffle to TRUE
#349 merged
Feb 7, 2025 -
docs: Improve website by adding overview pages
#347 merged
Feb 6, 2025 -
feat(cb-progress): print timestamps
#345 merged
Feb 6, 2025 -
docs: reoder pipeop torch docs
#344 merged
Feb 6, 2025 -
feat(nn_block): better avoidance of id clashes (#260)
#343 merged
Feb 6, 2025 -
Feat/tensor dataset
#341 merged
Feb 5, 2025 -
feat(ignite, jitting): Add parameter for trace-jitting and ignite optimizers
#329 merged
Jan 31, 2025
1 Pull request opened by 1 person
-
feat(layer): add tokenizers for categoricals and numerics
#348 opened
Feb 6, 2025
12 Issues closed by 1 person
-
Encoder PipeOp for categoricals / numerics
#165 closed
Feb 6, 2025 -
Add tokenizer categorical and tokenizer numeric as two separate `PipeOpTorch` objects
#333 closed
Feb 6, 2025 -
Improve display of LR Schedulers on the website
#326 closed
Feb 6, 2025 -
implement plotter for history state in mlr3viz
#227 closed
Feb 6, 2025 -
maybe also tag interop threads with `"threads"`
#296 closed
Feb 6, 2025 -
Progress callback should also print timestamps
#327 closed
Feb 6, 2025 -
Add converters that make it easier to create custom augementation and preprocessing operators.
#332 closed
Feb 6, 2025 -
Add AdamW optimizer
#301 closed
Feb 6, 2025 -
Improve performance
#323 closed
Feb 6, 2025 -
Document that interop threads need to be set seperately
#289 closed
Feb 6, 2025 -
Improve appearance of docs on website (e.g. for PipeOpTorchLinear etc.)
#339 closed
Feb 6, 2025 -
PipeOpBlock should avoid ID clashes in a smarter way
#260 closed
Feb 5, 2025
2 Issues opened by 1 person
-
Use `nn("` instead of `po("nn_")` in examples
#346 opened
Feb 6, 2025 -
Add vignette on performance
#342 opened
Feb 4, 2025
4 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
self attention pipeop
#102 commented on
Feb 4, 2025 • 0 new comments -
Invalid shape: better error handling
#223 commented on
Feb 5, 2025 • 0 new comments -
Outreach
#234 commented on
Feb 6, 2025 • 0 new comments -
Benchmark/rf use case
#294 commented on
Feb 6, 2025 • 0 new comments