FILTRIX Logo FILTRIX Find Your Edge →

FILTRIX / Lesson 01 of 4

How to Use FILTRIX

Your first trip through FILTRIX: build one historical sample, save it, and see how Context and Execution fit together.

Beginner 5 min read Updated 2026-10-07 5 min practice

Watch the walkthrough

Quick Start video walkthrough

2:07 · English · CC

Read the full video transcript

Welcome to Filtrix. This quick start connects the two main research tools. Context finds matching historical examples and describes their daily closes. Execution tests a specific entry and exit on the saved sample. Let us follow one simple exercise from start to finish.

After signing in, open Context from the navigation. Home also offers shortcuts to the main tools. Keep the app open beside the lesson so you can try each step. You will need available analysis quota to run the exercise.

Add one filter: symbol equals A A P L. Choose January first through December thirty first, twenty twenty-five, and keep the in-range band at zero point five to zero point eight. This is an interface exercise, not a stock recommendation. The sample comes from historical alert records, so it does not represent every trading day for this symbol.

Select Run Analysis. Check the matching record count and the usable sample, n, then inspect the Preview rows. Give the analysis a descriptive name and save All. Saving only a favorable closing bucket would select examples using information from the end of the day. Use the same saved context in the next step.

Open Execution and select the saved context. For this controls-only baseline, use twenty-five pairs, one-minute bars, Long, Open at nine thirty, and Close at sixteen hundred. Select Preview and inspect one completed trade. These settings demonstrate the controls; they do not establish a trading strategy. Reported profit and loss excludes trading costs.

Your goal is to complete the round trip and explain the two questions: where matching days closed, and what happened under specific execution rules. Try the practice task below. Then continue to the Context lesson for sample counts and buckets, followed by Execution for trade results and charts.

What You Will Learn

  • Find Context and Execution in the workspace.
  • Run a simple example and identify the usable sample.
  • Save all matching days and find the context in Execution.
  • Know which lesson to open next.

Before You Start

  • A FILTRIX account and available analysis quota.
  • A familiar ticker. We use AAPL for an interface exercise, not a trading recommendation.
  • A few minutes to try the steps in a second browser tab.
01

Create an account or log in

Open FILTRIX and sign in. If this is your first visit, create a free account first. You do not need to configure anything advanced before running your first analysis.

Action: Register with email/password or use Google sign-in.
02

Open Context and start with one symbol

Choose Context in the app navigation. Begin with one filter so you can see the workflow without managing a complex setup. In the Column field choose symbol, set Condition to equals, and enter AAPL. This searches the historical alert dataset; it does not request every AAPL trading day.

Action: Add symbol = AAPL. You can also paste the command below into Filter command and select Apply.
Paste into Filter command, then select Apply
symbol = AAPL
A single-symbol Context example in the current interface.
A single-symbol Context example in the current interface.
03

Run a small, repeatable exercise

Under Analysis Parameters, set Start Date to 2025-01-01 and End Date to 2025-12-31. Keep the In-range Band at 0.50–0.80. This band describes where the close sits within each daily range; it is not a trade return.

Action: Select Run Analysis. Note Total found in history and Included in calculation (n).
The example result. Counts can change as the historical dataset is updated.
The example result. Counts can change as the historical dataset is updated.
04

Save the sample you actually tested

Preview the matching rows, then use Save Analysis. A clear name makes the sample easy to find later. Use All for the rows to save, so the sample is not selected by how the day eventually closed.

Action: Name it Tutorial - AAPL 2025 (All), choose All, and select Save Analysis. If you already saved it, reuse it.
Save the full sample under a descriptive name.
Save the full sample under a descriptive name.
05

Move from the sample to execution rules

Open Execution and select your saved context. Context describes the daily outcomes of matching historical examples. Execution uses intraday bars to simulate a defined entry and exit. For a controls-only baseline, select 25 pairs, 1 minute, Long, Open at 09:30, and Close at 16:00. These settings demonstrate the interface; they do not establish a tradable strategy.

Action: Select Preview, then open one completed trade. Continue with the Context and Execution lessons to understand the numbers.
The saved Context is the input to Execution Analysis.
The saved Context is the input to Execution Analysis.

Your turn / about 5 minutes

Complete your first round trip

Keep a brief note of your inputs and what you observe.

Open FILTRIX in a new tab ↗
  1. Run symbol = AAPL for 2025-01-01 through 2025-12-31, with a 0.50–0.80 band.
  2. Write down Total found and n. Inspect at least one Preview row.
  3. Save All as Tutorial - AAPL 2025 (All), then select it in Execution.

You're done whenYou can find the same saved context in Execution and explain which question each analysis answers.

Pause before moving on

Check your understanding

Answer in your own words, then open each question to compare.

Which tool answers “where did matching days close”?

Context Analysis. Execution Analysis answers a different question: what happened under a particular entry and exit rule.

Does symbol = AAPL return every trading day for AAPL?

No. It filters the historical alert records available in FILTRIX. The usable daily sample depends on the matching records and data coverage.

Get unstuck

If something looks different

I cannot find my context in Execution.

Running Context does not save it automatically. Finish Run Analysis, name the result, select All, and save it. Then reopen Execution and select that context.

My results do not match the screenshot.

Check the symbol, date range, and band. Screenshots capture one dataset state; historical coverage can change. Follow the workflow rather than expecting a fixed count.

Common Mistakes to Avoid

  • Do not treat a tiny sample as proof of edge.
  • Do not replace exact filters with a loose story about the setup.
  • Do not skip execution testing when the context result looks promising.
  • Do not save every experiment. Save only setups you can explain and reuse.

Related lessons

Ready to test the setup?

Use the practice task to record your inputs, inspect the sample, and explain the result.

Go to the practice task ↑