WEBVTT

00:00:00.200 --> 00:00:02.661
A Trade Ideas alert is a starting question.

00:00:03.288 --> 00:00:07.061
To study it in Filtrix, turn the conditions into an exact filter

00:00:07.061 --> 00:00:07.746
definition.

00:00:08.478 --> 00:00:12.983
This lesson shows a simple example, the Collaborate import shortcut,

00:00:12.983 --> 00:00:16.408
and the checks that keep a historical test tied to the information

00:00:16.408 --> 00:00:17.661
you actually had.

00:00:18.267 --> 00:00:23.004
Consider a hypothetical setup: a gap of at least five percent and

00:00:23.004 --> 00:00:24.896
a price of at least ten dollars.

00:00:25.628 --> 00:00:29.842
In Filtrix, the corresponding fields are gap underscore gup and

00:00:29.842 --> 00:00:31.317
price underscore price.

00:00:31.851 --> 00:00:34.510
Use greater than or equal to for both.

00:00:35.136 --> 00:00:39.421
The numbers illustrate the syntax, not recommended trading thresholds.

00:00:40.047 --> 00:00:41.905
Both conditions must match.

00:00:42.533 --> 00:00:43.613
Open Context.

00:00:43.949 --> 00:00:47.641
Paste the example command from the written lesson into Filter command,

00:00:47.641 --> 00:00:48.860
then select Apply.

00:00:49.487 --> 00:00:53.145
Check that two rows appear with the expected columns, operators,

00:00:53.145 --> 00:00:53.969
and values.

00:00:54.596 --> 00:00:57.510
Applying the command replaces the current filter rows.

00:00:58.044 --> 00:01:01.527
You can also build the same definition manually with Add Filter.

00:01:02.133 --> 00:01:05.825
If you have a Trade Ideas Collaborate link, paste it into the same

00:01:05.825 --> 00:01:07.694
field and select Apply.

00:01:08.426 --> 00:01:11.932
The importer maps supported minimum and maximum conditions.

00:01:12.559 --> 00:01:15.217
It does not recreate the entire alert window.

00:01:15.751 --> 00:01:20.047
Exchanges and stock lists are not imported, and unsupported filter

00:01:20.047 --> 00:01:21.882
codes are reported as skipped.

00:01:22.613 --> 00:01:26.839
Compare the resulting rows with the original definition before continuing.

00:01:27.467 --> 00:01:30.033
Timing matters as much as the filter values.

00:01:30.567 --> 00:01:34.793
A price or volume condition observed at ten fifteen cannot justify

00:01:34.793 --> 00:01:36.198
an entry at nine thirty.

00:01:37.045 --> 00:01:40.923
Record when each condition became known, and use an execution rule

00:01:40.923 --> 00:01:42.350
consistent with that timing.

00:01:43.511 --> 00:01:47.540
Saving All avoids choosing days by their final close, but it cannot

00:01:47.540 --> 00:01:50.361
remove timing bias from the filters themselves.

00:01:50.967 --> 00:01:54.914
Choose research and validation periods before inspecting the result.

00:01:55.646 --> 00:02:00.394
Run Context, check the counts and underlying rows, and save All

00:02:00.394 --> 00:02:02.821
for a timing-consistent execution test.

00:02:03.552 --> 00:02:07.557
Keep a note of the filters, missing imported conditions, dates,

00:02:07.557 --> 00:02:08.393
and rules.

00:02:09.020 --> 00:02:12.155
Your finished exercise should let someone else reproduce what you

00:02:12.155 --> 00:02:14.558
tested, including its limitations.