A platform where people, from early stages of education to higher education,
can create and watch functional systems, physical, digital, or imaginary,
following a simple engine that everyone can use.
RealReplic is the Observatory: the application through which a learner watches a system run, tests it by changing a parameter, builds on it by solving a design challenge, and requests its physical replica. Systems are composed from a small set of primitives on a simple engine, so that a student in early education and a student in higher education can use the same tool.
This repository is part of the DT-HRES project, funded by EPICS in IEEE, and is developed by the Observatory division of Technical Arts. It lives in its own repository, separate from the twin it shows.
Its first system is DT-HRES-S, the digital twin of a hybrid renewable energy system. That repository keeps the twin (simulator, models, AutoCorrector, telemetry, hardware); this one keeps the platform and never duplicates it.
| Repository | Contains |
|---|---|
RealReplic |
Platform: user-facing application, composition engine, challenges, export and request flow |
DT-HRES-S |
Pilot system shown in the Observatory |
| Role | Person | GitHub |
|---|---|---|
| Supervisor | Dr. Rasikh Tariq | |
| Technical lead, DT-HRES project | Aaron C. | @Aaron-Cuevas |
| Lead, Observatory division | Braulio M. | @not-enough-tokens |
Funding: EPICS in IEEE.
Each system appears in the Observatory as four stages, traversed as chapters.
| Stage | What the learner does | DT-HRES-S pilot |
|---|---|---|
| Operation | Watches the twin run with its telemetry | Nodes N1 to N8 of the bench |
| Test | Varies one parameter and sees the response | Irradiance or ambient temperature |
| Build | Solves a design challenge and exports the solution | Panel, turbine and battery sizes above 90 % coverage of a community |
| Request | Asks for the physical instrument | Bench delivered unassembled, studied in stages HRES 1 to HRES 7 |
Measurements from a requested instrument return to its system as validation data.
Details: docs/user-flow.md.
Specification stage. The user flow and the interface are defined; no code has been written and no technology has been adopted. Technology choices belong to the development team and are recorded in docs/decisions.md.
Requirements that any choice must meet:
- usable offline; for DT-HRES-S, served from the local network of its control unit
- usable from a phone browser in vertical 9:16 format
- open license, no paid dependencies
- reads each system through that system's own repository, without duplicating it
app/ application source (empty until development starts)
docs/
user-flow.md stages, interface rules, challenges
decisions.md technology decisions and their reasons
CONTRIBUTING.md branches, commits, reviews
Observatory division. Add yourself in your first pull request.
| Name | GitHub username | Institution | Role |
|---|---|---|---|
| @not-enough-tokens | Division lead | ||
CC BY-NC-SA 4.0. See LICENSE.