Skip to content

Comments

Fix inconsistent model training approach in trian_and_predict function#72

Open
sohampirale wants to merge 1 commit intoruxailab:mainfrom
sohampirale:fix/hyperparameters_use_calib_validation
Open

Fix inconsistent model training approach in trian_and_predict function#72
sohampirale wants to merge 1 commit intoruxailab:mainfrom
sohampirale:fix/hyperparameters_use_calib_validation

Conversation

@sohampirale
Copy link

Summary

This PR fixes an inconsistency in the trian_and_predict function where models were not being handled according to their hyperparameter configurations.

Fixes : #71


Solution

Updated the conditional logic to properly align model usage with hyperparameter availability:

  • IF block (simple fitting): Models without hyperparameters in config.py

    • "Linear Regression"
    • "Random Forest Regressor"
  • ELSE block (GridSearchCV): Models with hyperparameters in config.py

    • "Ridge Regression", "Lasso Regression", "Elastic Net", "Bayesian Ridge", "SGD Regressor", "Support Vector Regressor"

Files Changed

  • app/services/gaze_tracker.py: Updated the conditional logic in trian_and_predict function

Screenshots (tested with all 3 models)

  • Elastic Net
Screenshot from 2026-02-15 22-55-01
  • Support Vector Regressor
Screenshot from 2026-02-15 22-56-05
  • Random Forest Regressor
Screenshot from 2026-02-15 22-56-35 Screenshot from 2026-02-15 22-58-28

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.

Fix inconsistent model training approach in trian_and_predict function

1 participant