Skip to content

feat: add ThermalScope signal experiment app - #188

Closed
WuShang-d wants to merge 1 commit into
casosorg:masterfrom
WuShang-d:codex/thermalscope-store
Closed

WuShang-d wants to merge 1 commit into
casosorg:masterfrom
WuShang-d:codex/thermalscope-store

Conversation

@WuShang-d

@WuShang-d WuShang-d commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Add the self-contained ThermalScope application under apps/thermalscope, a built-in marketplace template, and a separate image workflow. Simple mode starts a bounded thermal-signal experiment after an authorized connection; professional mode keeps manual input. Results, cancellation and data/report exports are included.

The source can subsequently move to a dedicated repository following the SegScope arrangement. The independently implemented temperature demonstration does not redistribute the unlicensed research artifact or claim reliable communication.

Verification

  • CasOS: Go build/vet, existing i18n deduplication tests, frontend lint and production build passed.
  • Application: Linux build/package on pkusgx, parser checks, 24 non-heating Python checks, and prior browser flow checks passed.
  • Built-in template loading, string environment values for both channel settings, and Helm lint/render passed.
  • Image archive checksums, isolated image-rootfs startup, and the Docker image startup check in GitHub Actions passed. The real thermal run did not separate the calibration signals; unknown bits remain unknown.

@WuShang-d

Copy link
Copy Markdown
Contributor Author

I have initially placed ThermalScope under apps/thermalscope so the application can be reviewed here. Could you arrange a dedicated repository under casosorg, following the SegScope repository arrangement?

The app keeps its own Go/JavaScript manifests, Dockerfile, runner and Helm chart to make that move straightforward. The platform additions are limited to store/builtin/thermalscope.yaml and .github/workflows/thermalscope-image.yml.

@hsluoyz hsluoyz closed this Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants