# Off-line processing and modeling

## Off-line processing and modeling

Process of off-line aggreagetes computing and modeling should be repeated at fixed intervals (induced automatically or manually). For every model an analytical table is created. The table contains 1 line for each user, that fulfils trigger condition and has counted target. For every analytical table, the Automatic Business Modeler builds a model. Deployed models and information about used variables (model's signature) are saved to metadata. The method inducing off-line processing starts an API ABM method, that enable to build a model in only 1 query (for more information see [ABM documentation](https://algolytics-technologies.gitbook.io/algolytics/abm)). A table with aggregates is an input table to ABM process, that selects suitable variables and calculates optimal model automatically. This method also enables saving the aggregates table for further analysis or manual modeling. For this purpose, a GDBase alias and a table name must be given.

## Scheduling an off-line processing <a href="#scheduling-an-off-line-processing" id="scheduling-an-off-line-processing"></a>

Process of building models can be scheduled. Scheduling is done through inducing an API adding model request (see [Examples of API operations](/algolytics/event-engine-user/examples-of-api-operations.md). After first build of a model, the task is scheduled for the next day. If model building succeed and the model will be implemented (accurate number of positive targets, accurate quality of the model based on ROC curve), then next model building is scheduled for the next week.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://algolytics-technologies.gitbook.io/algolytics/event-engine-user/off-line-processing-and-modeling.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.