You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Accept missing values (null / empty CSV cells) in fit and predict #61
Real tables have missing values, and both TabPFN and TabICL handle NaN natively. Today there's no way to send one:
JSON:train_X/test_X are list[list[float]], so null gets a 422. A NaN literal isn't valid JSON, and the gateway's orjson parser answers 400.
CSV upload:np.loadtxt rejects empty cells. The text nan does parse.
Users must impute before sending, which loses information the models would use. The real-data eval (#59) had to median-fill Titanic, about 3% of cells.
Proposal:
Accept float | None in train_X/test_X and map None to NaN.
In CSV, treat empty cells, NA and nan as NaN.
The Parquet path (see the large-uploads issue) carries nulls natively.
Add tests for both backends: NaN in train only, in test only, and a whole column missing.
Activity
feat: missing values in fit/predict (#61); integer targets and many-c…