Skip to content

feat: add validation_frequency option to fine-tuning (#811)#816

Open
Anakintano wants to merge 1 commit intoPriorLabs:mainfrom
Anakintano:fix/issue-811
Open

feat: add validation_frequency option to fine-tuning (#811)#816
Anakintano wants to merge 1 commit intoPriorLabs:mainfrom
Anakintano:fix/issue-811

Conversation

@Anakintano
Copy link

Resolves #811

Summary

  • Add validation_frequency: int | None = 1 parameter to FinetunedTabPFNBase, FinetunedTabPFNClassifier, and FinetunedTabPFNRegressor
  • validation_frequency=None: disables validation entirely (also disables early stopping, emits UserWarning if early_stopping=True)
  • validation_frequency=N: runs validation every N epochs
  • validation_frequency=1 (default): preserves existing behaviour

Test plan

  • Smoke-tested instantiation with None, N, and default values
  • Default of 1 is backward compatible with no breaking changes

@Anakintano Anakintano requested a review from a team as a code owner March 12, 2026 12:18
@Anakintano Anakintano requested review from Innixma and removed request for a team March 12, 2026 12:18
@chatgpt-codex-connector
Copy link

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

@CLAassistant
Copy link

CLAassistant commented Mar 12, 2026

CLA assistant check
All committers have signed the CLA.

- Add `validation_frequency: int | None = 1` parameter to
  `FinetunedTabPFNBase`, `FinetunedTabPFNClassifier`, and
  `FinetunedTabPFNRegressor`
- When `validation_frequency=None`, validation is disabled entirely
  (also disables early stopping with a UserWarning)
- When `validation_frequency=N`, validation runs every N epochs
- Default of 1 preserves existing behaviour (validate every epoch)

Closes PriorLabs#811
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds a validation_frequency parameter to control validation during fine-tuning. The implementation is well-structured. I've added one comment to suggest validating the new parameter to prevent potential runtime errors. It would also be beneficial to add unit tests for this new functionality to ensure its correctness and prevent regressions.

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.

Add validation options to fine tuning

2 participants