update pages

Author: zh1peng

docs/_build/doctrees/environment.pickle

@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
-config: 6504529fc22095a1821ce59b9c36fde9
+config: 4cd82dbd7b3420fc9226beea123ec288
 tags: 645f666f9bcd5a90fca523b33c5a78b7

docs/_build/doctrees/index.doctree

@@ -201,7 +201,7 @@
   <input type="hidden" name="check_keywords" value="yes">
   <input type="hidden" name="area" value="default">
 </form>
-<div id="searchbox"></div><div class="sidebar-cta entries-box">
+<div id="searchbox"></div><div class="sidebar-scroll"><div class="sidebar-cta entries-box">
   <ul style="list-style: none; padding-left: 0;">
     <li><a href="https://taskbeacon.github.io/">Taskbeacon Home</a></li>
   </ul>
@@ -237,7 +237,7 @@
 <li class="toctree-l1"><a class="reference internal" href="../py-modindex.html">Module Index</a></li>
 </ul>
 
-</div>
+</div></div>
       </div>
 
     </div>

docs/_build/doctrees/tutorials/build_stimulus.doctree

@@ -19,8 +19,6 @@ Features
 
 Start with one of the tutorials below or explore the API reference.
 
-Tutorials
----------
 .. toctree::
    :maxdepth: 1
    :caption: Tutorials
@@ -36,8 +34,8 @@ Tutorials
    tutorials/utilities
    tutorials/llm_client
 
-中文教程(Chinese Tutorials)
----------
+
+
 .. toctree::
    :maxdepth: 1
    :caption: 中文教程(Chinese Tutorials)
@@ -52,8 +50,7 @@ Tutorials
    tutorials/cli_usage_cn
    tutorials/llm_client_cn
 
-Indices and tables
----------
+
 .. toctree::
    :maxdepth: 1
    :caption: Indices and tables

docs/_build/doctrees/tutorials/get_subinfo.doctree

@@ -85,7 +85,7 @@ stim_bank = StimBank(win, config=stim_config)
 | movie   | MovieStim | Video playback                        |
 | sound   | Sound     | Audio playback using PsychoPy Sound   |
 
-```{Note}
+```{note}
 A good place to learn about stimulus parameters is the PsychoPy Visual API page (https://www.psychopy.org/api/visual/). We will add support for additional stimulus types as we encounter them during the development of new tasks.
 ```
 
@@ -232,7 +232,7 @@ stim_bank.preview_all()                    # display or play every registered st
 stim_bank.preview_selected(["fixation"])   # only the specified stimuli
 stim_bank.preview_group("feedback_")       # all stimuli with the "feedback_" prefix
 ```
-```{Tip}
+```{tip}
 Use previews to catch layout or styling issues early, rather than during live trials.
 ```
 

docs/_build/html/.buildinfo

@@ -430,7 +430,7 @@ cue.to_dict(trial_data)
 - `highlight_stim` maps each key to a visual cue (e.g., a frame or dot).
 - If `dynamic_highlight=True`, each new key press updates the highlight until the window ends.
 
-```{Tip}
+```{tip}
 You can also pass a `dict` to `response_trigger` to send different trigger codes per key.
 ```
 
@@ -608,7 +608,7 @@ make_unit('resp_chain', win, kb) \
     .on_end(lambda u: u.log_unit()) \
     .run()
 ```
-```{Warning}
+```{warning}
 In most cases, using `.show()`, `.capture_response()`, and `.wait_and_continue()` covers the vast majority of task requirements and has been extensively tested. Lifecycle hooks offer maximum flexibility, but they are less commonly used and have seen less practical validation. We did not test their usage extensively. Only opt for manual hooks when you need custom behavior beyond the built-in methods—and proceed with caution.
 ```
 
@@ -680,7 +680,7 @@ fb.set_state(prefix='special', hit=True)
 | Custom  | 'special'    | special\_hit                   |
 
 
-```{Tip}
+```{tip}
 `set_state` is **Chaining**: it returns the same `StimUnit`, so you can chain calls:`unit.set_state(block=2, trial=5).set_state(condition='win')`
 ```
 
@@ -709,7 +709,7 @@ Several `StimUnit` methods populate internal state without explicit `set_state()
 
 Use this table to quickly see what state values are filled in automatically, so you know which additional `set_state()` calls you might still need.
 
-```{Note}
+```{note}
 For `capture_response()`, the `hit` means the response was a correct key press.
 ```
 

docs/_build/html/_modules/index.html

@@ -415,7 +415,7 @@ cue.to_dict(trial_data)
 - `highlight_stim` 将每个按键映射到一个视觉提示（例如，一个框或一个点）。
 - 如果 `dynamic_highlight=True`，每次新的按键都会更新高亮，直到窗口结束。
 
-```{Tip}
+```{tip}
 您还可以将一个 `dict` 传递给 `response_trigger`，以便为每个按键发送不同的触发码。
 ```
 
@@ -593,7 +593,7 @@ make_unit('resp_chain', win, kb) \
     .on_end(lambda u: u.log_unit()) \
     .run()
 ```
-```{Warning}
+```{warning}
 在大多数情况下，使用 `.show()`、`.capture_response()` 和 `.wait_and_continue()` 涵盖了绝大多数任务需求，并经过了广泛测试。生命周期钩子提供了最大的灵活性，但它们不太常用，并且实际验证较少。我们没有广泛测试它们的用法。只有当您需要超出内置方法的自定义行为时才选择手动钩子——并谨慎行事。
 ```
 
@@ -663,7 +663,7 @@ fb.set_state(prefix='special', hit=True)
 | 原始 | '' | hit, delta |
 | 自定义 | 'special' | special_hit |
 
-```{Tip}
+```{tip}
 `set_state` 是 **可链式调用的**：它返回同一个 `StimUnit`，所以您可以链式调用：`unit.set_state(block=2, trial=5).set_state(condition='win')`
 ```
 
@@ -690,7 +690,7 @@ fb.set_state(prefix='special', hit=True)
 
 使用此表可以快速查看哪些状态值是自动填充的，这样您就知道可能还需要哪些额外的 `set_state()` 调用。
 
-```{Note}
+```{note}
 对于 `capture_response()`，`hit` 表示反应是正确的按键。
 ```