> For the complete documentation index, see [llms.txt](https://docs.graphite-note.com/graphite-note-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graphite-note.com/graphite-note-documentation/graphite-note-models/advanced-ml-model-settings/regressors/frequency-alignment.md).

# Frequency alignment

#### Frequency Alignment: Matching Regressors to Your Model’s Time Granularity

Every regressor must supply exactly one value for each timestamp in your target series—no more, no less. Graphite Note enforces this 1:1 rule to ensure your external features line up perfectly with what you’re forecasting.

* Daily models → one regressor value per date
* Hourly models → one regressor value per hour
* Weekly models → one regressor value per week, etc.

If your raw data has a finer granularity than your model (e.g., minute-level web clicks for a daily forecast), you must aggregate it (sum, mean, max, etc.) so each day has a single number. Conversely, you can’t “stretch” a single daily value into multiple hourly slots without interpolation—each timestamp needs its own authentic input.\
\
***Numerical Regressors (e.g. Cost per Unit)***

* *Aggregate before uploading.*
* *Choose a summary statistic that fits your use case:*
  * *Average (mean unit cost)*
  * *Sum (total cost volume)*
  * *Max/Min (peak or baseline cost)*
* *Result: one number per date (or hour/week) that aligns 1:1 with your target.*

\
***Categorical Regressors (e.g. Category Code, Weather Label)***

* *Ensure only one category value per timestamp.*
* *If multiple occur:*
  * *Select the most representative label (e.g., “predominant” weather condition),*
  * *Encode logic-based rules (e.g., if any “Rain” occurs → is\_Rain = 1),*
  * *Or use proportions: % Category A = count(A) ÷ total.*

By strictly aligning frequencies—one regressor row for each target timestamp—you eliminate timing mismatches and give your model clean, reliable inputs.


---

# 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.graphite-note.com/graphite-note-documentation/graphite-note-models/advanced-ml-model-settings/regressors/frequency-alignment.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.