> For the complete documentation index, see [llms.txt](https://docs.flock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flock.io/flock-products/fl-alliance/task-lifecycle-deep-dive/3.-fl-aggregation-and-evaluation.md).

# 3. FL Aggregation and Evaluation

Then, each voter gathers the local models from all proposers. These models are then aggregated into the latest global model using a weighted averaging approach. Each voter then proceeds to evaluate the aggregated model, utilising their own local testing datasets. This evaluation phase involves the computation of a local validation score, which functions as a criterion for assessing the model’s performance. These individual validation scores

are then submitted to a smart contract for aggregation. Following the aggregation, the aggregated score is compared with the previous round’s score, to assess progress or decline in model performance. The smart contract then determines the next steps for the aggregated model based on these scores: if there is an improvement in performance score, the system will proceed to the next phase of training; if there is a decline, another round of training, aggregation and evaluation will begin using the validated model from the previous round. 

After receiving all reported voting results from the voters, the aggregator (any participant can call the function through the smart contract) will calculate the aggregated voting result.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flock.io/flock-products/fl-alliance/task-lifecycle-deep-dive/3.-fl-aggregation-and-evaluation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.