ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
AI & Law — BYU Law Exercise Launcher
An interactive classroom tool for running live AI law exercises.
The launcher opens to a home screen where you select which exercise to run. All exercises share a unified appearance and settings system.
A simulated Silicon Slopes panel on the state of AI regulation. Students are organized into groups, assigned panelist topics, and the instructor moderates a live Q&A with a built-in timer.檢視完整 README ↗An interactive classroom tool for running live AI law exercises.
The launcher opens to a home screen where you select which exercise to run. All exercises share a unified appearance and settings system.
A simulated Silicon Slopes panel on the state of AI regulation. Students are organized into groups, assigned panelist topics, and the instructor moderates a live Q&A with a built-in timer.
Setup
type ("presentation" or "question"), script (moderator/question text), and prompt (panelist preparation prompt). Publish as CSV and paste the URL into the app.Q) or Quick Fill + Start (W) for fast testing.? for full in-app instructions.Moderator view
← / → or the nav buttons in the header.A cold-call exercise where students are drawn at random and assigned an AI product scenario to advise on. The instructor then reveals the priority legal issues for discussion.
Setup
title, text, top legal risks).Moderator view
← / →.L.An integrated visualization tool for exploring how word embeddings work — plot words in 3D space to see how numbers capture semantic meaning and relationships between concepts.
Setup
word (or name), x, y, z — values 0.0–1.0. Publish as CSV.Controls
div contents with an <img> tag pointing to your form's QR code).Future: live in-class participation The current workflow — student fills Google Form → sheet updates → instructor clicks Refresh — works well but requires a manual refresh step. Eventually the goal is for students to visit a page, enter their values, and see the plot update live for the whole class without any form or refresh. See "Live Participation" section below.
| Key | Action |
|---|---|
S | Open Settings / Appearance |
M | Go to Home screen |
Esc | Close any open popup |
| Key | Action |
|---|---|
1 | Open AI Regulation Panel |
2 | Open Product Counsel Exercise |
| Key | Action |
|---|---|
Q | Quick Fill names |
W | Quick Fill + Start |
Enter | Start Panel |
A | Toggle Advanced section |
? | Open Help |
| Key | Action |
|---|---|
← / → | Previous / Next panel |
Space | New question |
R | Return to Setup |
T | Toggle Timer |
C | Toggle Count Up / Down |
F | Start / Pause Timer |
G | Reset Timer |
? | Open Help |
| Key | Action |
|---|---|
Q | Quick Fill names |
Enter | Start |
| Key | Action |
|---|---|
← / → | Previous / Next result |
Space | Next result |
L | Toggle Priority Legal Issues |
R | Reset (return to Setup) |
T | Toggle Timer |
F | Start / Pause Timer |
G | Reset Timer |
S from any screenThe current 3D Plotter workflow relies on Google Forms → Google Sheets → CSV polling. The long-term goal is a smoother in-class flow: a student opens a URL on their phone, rates a word on three sliders, hits submit, and everyone in the room watches the point appear on the instructor's projected plot — no forms, no manual refresh.
How this would work
The most practical approach is a small backend with WebSockets (or Server-Sent Events):
Plotly.extendTraces.An alternative that avoids a custom backend entirely is a Google Apps Script Web App with a webhook trigger: the form's onFormSubmit Apps Script trigger calls a published Apps Script endpoint, which pushes the new row to a Firebase Realtime Database (or similar); the plotter listens to Firebase for changes. This adds complexity but keeps everything inside Google's ecosystem.
A simpler polling approach (no WebSockets) — auto-refresh the CSV every 5–10 seconds — is the easiest to implement and requires no backend change. It introduces a short lag but may be acceptable for a classroom setting.