Add a README note about the TabFM technical report status#67
Open
MayVerse4 wants to merge 1 commit into
Open
Conversation
MayVerse4
requested review from
abhidas,
erzel,
rajatsen91,
siriuz42,
tamannarayan and
weihaokong
as code owners
July 11, 2026 14:51
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi maintainers! This is a small documentation-only update for Issue #64 in google-research/tabfm.
I added a short “Technical Report” section to the README clarifying the current status: there is not a standalone technical report or paper included in the repository at this time, and the section can be updated with a link if/when one becomes available. This directly addresses the request for information about model architecture, training pipeline, datasets, and evaluation methodology without touching any code or architecture.
No tests were run since this is a README-only change. Happy to adjust the wording if you’d prefer a different status note or timeline language.
Fixes #64