fix the conversion - #1
Conversation
Scheme/Node/Bind data model, the annbatch-backed Loader and control-rooted EvalLoader, obs factorization + in-memory materialization, and splitting, with the data test suite. Data-only branch — foundation (nn/training) and metrics live on the `rest` branch; this branch is meant to land on main on its own. Co-Authored-By: Claude Opus 4.8 <[email protected]>
Keep the data branch focused on the training Loader; the control-rooted EvalLoader (and its metrics-integration test) are deferred and will be re-added later as a second loader reusing the shared _SchemeReader / _backend layer. Removes _eval_loader.py, test_eval_loader.py, test_metrics_over_loader.py, and the EvalLoader export. Co-Authored-By: Claude Opus 4.8 <[email protected]>
…ritten by ai I dont have time to unslopify)
Metrics moved here (off the data branch) so `data` stays a clean, data-only unit to bring to main. Co-Authored-By: Claude Opus 4.8 <[email protected]>
|
can you give me an example? ideally the datasets are preprocessed so that even if a categorical is not present in that dataset is should have under |
|
Do you agree on this? Maybe I can make it clearer that I expect here in cateogoricals to have the same labeling metadata ie unified categoricals. |
|
To me this is an easy fix to make it more robust. It would be nice to make it explicit that one should unify the dataset in such a way. Maybe either have unify.py logic in also scfit instead of just cf-train and delete this logic here, or make it working now. Either way, I think we should fix this simply bc now it's not doing what it's intended to do. Output for pandas version >3 |
ee4b393 to
43414a8
Compare
Pandas refuses to assign a
Categoricalwith categories different from the target's