Thesis & research · Method

Choosing a machine learning model for your thesis.

Why the most sophisticated architecture is usually the wrong answer, and how to pick one you can defend in front of a panel.

Kleio Software10 min read

There is a pattern in academic machine learning projects that is easy to predict and easy to avoid. The student picks the most advanced method they have heard of, trains it, gets a number, and then cannot answer the question every panel asks: why this one?

Model selection is not a search for the best algorithm in the abstract. It is a search for the method that fits your problem type, your dataset size, and your ability to explain it. Those three constraints usually narrow the field to two or three sensible candidates before you write any code.

This guide is the reasoning to walk through, in order.

Start with your problem type — it eliminates most options immediately

Before anything else, name what your model outputs. This single question removes most of the field.

A number → regression
Yield, price, strength, demand, consumption. Candidates: linear regression as your baseline, then tree ensembles, then a neural network only if those are clearly insufficient.
A category → classification
Material type, risk band, pass or fail, disease present or absent. Candidates: logistic regression as baseline, then decision trees and ensembles, then neural networks.
A number over time → forecasting
Anything indexed by date. This is its own family, and the critical difference is that you must validate chronologically. A random split here is a methodological error a panel will catch.
Groups with no known labels → clustering
Customer segments, site typologies. Note that there is no accuracy to report, so the defense rests entirely on justifying the number of clusters and interpreting them.
Images → computer vision
Classification, detection or segmentation on visual input. Almost always transfer learning from a pretrained model rather than training from scratch, because you will not have enough labeled images to do otherwise.
Text → natural language processing
Classification, sentiment, topic modeling. For Filipino and Taglish, be aware that most off-the-shelf tooling underperforms, which is a limitation worth documenting and often a contribution in itself.

Then let your dataset size narrow it further

This is the step students skip, and it is the one that most often decides whether a model generalizes or merely memorizes. Model capacity has to be matched to how much data you have.

A rough guide for tabular problems. Under a few hundred rows, stay with simple, well-regularized methods — linear and logistic regression, small decision trees. A few hundred to a few thousand rows is where tree ensembles like random forests and gradient boosting are typically strongest, and on tabular data they frequently outperform neural networks at this scale. Beyond several thousand rows, a neural network becomes a reasonable candidate rather than an aspiration.

The number of input variables matters alongside the row count. Many variables on few rows is the classic overfitting setup: the model finds patterns in noise, reports excellent training performance, and fails on anything new.

This is why our geotextile project used a smaller model deliberately. On a few hundred rows, that is the defensible choice, and the thesis argued it explicitly rather than apologizing for it.

Always train a baseline first

This is the single most valuable habit in an academic machine learning project, and it costs almost nothing.

Before your intended model, train the simplest reasonable thing: linear or logistic regression, or even a rule that always predicts the majority class. Record its performance. That number is your floor.

It does two things. It tells you whether your sophisticated model is actually contributing anything — sometimes it is not, which is a genuine finding worth reporting. And it hands you a complete answer to the why-this-method question: because I compared it against a simpler alternative and it performed measurably better on held-out data.

Occasionally the baseline wins. Report that. A thesis showing that a simple model performs as well as a complex one on this problem is a real result, and defending it honestly is far stronger than quietly discarding it.

Weigh how much you need to explain the model's reasoning

In some fields, knowing which factors drove a prediction matters as much as the prediction. In medicine, education and policy research, a model that cannot tell you why is often not useful even when it is accurate.

Linear and logistic regression are the most interpretable: each coefficient has a direct reading. Decision trees can be inspected as a set of rules. Tree ensembles are partly interpretable through feature-importance measures. Neural networks are the hardest to interpret directly, and the tooling for explaining them adds work.

If your research question is partly about which factors matter, that pushes you toward the interpretable end. Do not treat this as a compromise; for a great many research questions the interpretable model is the correct scientific choice, not the fallback.

How to justify your choice in the defense

Your justification should rest on evidence you generated, not on the literature alone. A defensible answer has four parts, and you should be able to give it in under a minute.

What the problem type is and what that ruled out. What your dataset size and dimensionality implied about model capacity. What baselines you compared against and how they performed. Why the chosen model's advantage was worth its added complexity — including on interpretability if that matters in your field.

The failure mode to avoid is a justification that appeals only to novelty or popularity. “Deep learning is the current state of the art” invites the obvious follow-up: state of the art on what data, at what scale, and is that your situation? On a few hundred rows it is usually not.

Prepare for the limitations question too, because it is coming. Know what your model does badly, what happens with inputs outside its training range, and how much more data you would need to do better. Answering that clearly reads as competence, not weakness.

Want the choice made properly, with the evidence to back it?

Kleio builds machine learning models for thesis and capstone projects, including the baseline comparisons and evaluation a panel will ask for, and walks you through every decision so you can explain it in your own words.

AI for thesis & capstone projects

Related questions

The follow-ups people ask after reading this.

Should I use a neural network for my thesis?

Only if your data supports it and it beats a simpler baseline. On tabular datasets of a few hundred to a few thousand rows, gradient-boosted trees and random forests frequently outperform neural networks, and they are easier to justify. Neural networks earn their place on large datasets, images, and text.

Is it bad if my simple model performs as well as my complex one?

No, it is a result. A finding that a simpler method matches a more complex one on your problem is genuinely informative and entirely defensible. Report it honestly. Panels respond much better to that than to a complex model presented without comparison.

How many models should I compare in my thesis?

Two or three, chosen for a reason, beats a table of ten chosen at random. A simple baseline, your intended model, and possibly one intermediate option is a standard and defensible structure. What matters is that you can explain why each candidate was in the running.

What if my model's accuracy is low?

Low accuracy is a result too, provided the methodology is sound and you can explain why. Sometimes the honest finding is that the available inputs do not predict the outcome well, which is worth knowing. What damages a defense is inflated accuracy from a methodological error such as data leakage or testing on training data.

Do I need to explain the mathematics of my model?

Usually not the derivations, but you do need the concept: what the model is learning, what its inputs and outputs are, roughly how it arrives at a prediction, and where it is likely to fail. If you cannot explain it in plain language, you do not yet understand it well enough to defend it.

Still have a question this didn't answer?

Bring it to a free discovery call. No pitch, straight to the developer, and an honest answer even when it is that we're not the right fit.

Book a free discovery call