> For the complete documentation index, see [llms.txt](https://docs.tidelight.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tidelight.app/untitled-zh/cha-kan-hui-hua-zhi-jian-de-xin-hao-4.md).

# 查看会话之间的信号

## 测试这个想法。

## 尊重证据。

在 Bitget Reality 股票代币和美股永续市场上测试可审查的规则。将趋势、均值回归、突破和盘后思路与已完成蜡烛线进行比较，并考虑成本、滚动检验和按时间顺序划分的留出集。符合条件的运行至少需要 60 天历史数据和 30 天样本外数据。

* 公开 Bitget 蜡烛线
* 确定性信号
* 私有已保存运行

**最小留出期**\
**30 天以上**

事件 *→* 证据 *→* 曝险 *→* 情景 *→* **决策**

### 先测试规则，再测试其边界。

**仅限纸上研究**

Reality rToken · 美股现货 · 永续合约

Bitget Reality 股票代币。该市场可为 Nightwatch 现货模拟账户提供数据。

### 从一个市场想法开始。

描述你想测试的行为。Tidelight 将其映射为一条可审查规则，然后在一个 Reality rToken 上结合成本和单独的留出窗口进行回放。

**你想测试什么？**

0 /800 · 建议只是假设，不是业绩声明。\
起草一个可测试的想法 ↗

* ALPHA 规则
* 趋势 · SMA 20/50
* 均值回归 · RSI 14
* 动量 · 20/10 通道
* 盘后 · 周末漂移
* 趋势回调 · EMA / RSI
* 半导体 · 成交量突破
* 20 周期趋势高于 50 周期趋势。
* Reality rToken 符号
* 蜡烛线间隔
  * 1 小时
  * 4 小时
  * 1 天
* 运行留出测试 ↗

**代表性验证集**

* NVIDIA · rToken
* AMD · rToken
* Tesla · rToken
* Apple · rToken
* Microsoft · rToken

运行完整矩阵 ↗

### 你可以审查并回放的规则。

在六个固定规则家族中选择：趋势、均值回归、价格通道、盘后漂移、趋势回撤，以及经成交量确认的半导体突破。每次只回放一个已验证的 Bitget 市场；篮子比较会选出训练领先者，但不会建模持续轮换。信号使用已完成的蜡烛线，在下一个可交易开盘时模拟，并包含估算的手续费和滑点。生成的假设仅选择已实现的规则。

|             |           |
| ----------- | --------- |
| **20 / 50** | 趋势参考      |
| **66 / 34** | 训练集与留出集划分 |
| **0.15%**   | 假定单边成本    |

{% hint style="info" %}
历史回放不是预测。结果不包含股息、发行方行为和订单簿流动性；美股永续结果也不包含资金费率、保证金和强平。不会下单。
{% endhint %}

### 登录以保留私有运行历史。

无需登录也可检查方法；保存结果仅限账户范围。

[登录 ↗](/untitled-zh/cha-kan-hui-hua-zhi-jian-de-xin-hao-11.md)


---

# 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.tidelight.app/untitled-zh/cha-kan-hui-hua-zhi-jian-de-xin-hao-4.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.