further work and refinements
This commit is contained in:
@@ -4,18 +4,29 @@
|
||||
|
||||
\section{Results}\label{sec:results}
|
||||
|
||||
The previous section detailed the design and implementation of our ovulation prediction pipeline,
|
||||
We begin by comparing the overall performance of all trained models and baselines using four key evaluation metrics:
|
||||
mean absolute error (MAE), mean squared error (MSE), and the coefficient of determination (\(R^2\)) for the regression target,
|
||||
as well as the metrics for their respective sub-intervals.
|
||||
Figure~\ref{fig:results_performance_overview_by_model_type} provides an overview of these metrics across all model types.
|
||||
|
||||
Overall, transformer-based models consistently outperformed LSTM variants and baseline methods across most evaluation criteria.
|
||||
Among the baselines, [e.g., "the rule-based method"] showed the weakest performance,
|
||||
while the [e.g., "windowed logistic regression"] performed competitively in certain contexts.
|
||||
Differences across models were most pronounced in MSE and \(R^2\),
|
||||
indicating that advanced architectures better captured higher-order dynamics and reduced large prediction errors.
|
||||
|
||||
The previous section detailed the design and implementation of our fertility prediction pipeline,
|
||||
including data preprocessing, feature engineering, input encoding, and the development of several deep learning architectures.
|
||||
We now present the results of our evaluation, focusing on the predictive accuracy of the proposed models across different temporal resolutions,
|
||||
cycle types, and user histories.
|
||||
cycle types and use cases.
|
||||
Model performance is assessed using both overall metrics and biologically targeted subintervals,
|
||||
allowing for a nuanced comparison of approaches and their practical relevance to real-time fertility forecasting.
|
||||
Additionally, model performance is compared to the three baseline models introduced.
|
||||
|
||||
% provide information about the training behaviour and statistic of the different models
|
||||
% provide information about the training behaviour and statistic of the different models??
|
||||
|
||||
\subsection{Overall Model Performance Across Architectures}\label{subsec:overall_model_performance_across_architectures}
|
||||
|
||||
|
||||
\begin{figure}
|
||||
\centering
|
||||
\includegraphics[width=0.9\textwidth]{resources/figures/results/model_performance_overview}
|
||||
@@ -47,7 +58,6 @@ allowing for a nuanced comparison of approaches and their practical relevance to
|
||||
\end{landscape}
|
||||
|
||||
|
||||
|
||||
% show why I selected the individual input configs for model config training
|
||||
% selected by best mse fertility, use 2nd best, as it provides basically the same performance, but more input data for more complex model configs
|
||||
|
||||
@@ -59,7 +69,7 @@ allowing for a nuanced comparison of approaches and their practical relevance to
|
||||
|
||||
\subsubsection{Comparison with Baselines}\label{subsubsec:fert_comparison_with_baselines}
|
||||
|
||||
\subsection{Ovulation-Over Prediction Accuracy}\label{subsec:ov_over_prediction_accuracy}
|
||||
\subsection{Ovulation-Over Prediction Accuracy}\label{subsubsec:ov_over_prediction_accuracy}
|
||||
|
||||
\subsubsection{Performance around Ovulation}\label{subsubsec:ov_over_performance_around_ovulation}
|
||||
|
||||
@@ -81,5 +91,4 @@ allowing for a nuanced comparison of approaches and their practical relevance to
|
||||
|
||||
\subsubsection{Pregnancy Use-Case Results}\label{subsubsec:use_case_pregnancy_results}
|
||||
|
||||
|
||||
\subsection{Summary of Key Findings}\label{subsec:summary_of_key_findings}
|
||||
|
||||
Reference in New Issue
Block a user