Potential energy savings.
Where data movement dominates, moving fewer bytes could produce significant energy savings. The opportunity grows with repeated traffic and storage at scale.
Deep SIML Labs / StudioInvited beta
Keep the meaning.
Move fewer bytes.
Less data to move and store creates an opportunity for lower energy use. Studio turns your existing enums into compact, verifiable payloads and code you can build with.
Rust · Python · C++ · Email sign-in · Invited beta
YOUR ENUMSREVIEWPACKED CODEMEASURE
Why compact data matters
Spend less on
moving the same meaning.
Repeated states and commands often need only a few bits. Carrying them in larger representations can mean more memory traffic, storage and network transfer.
Less integration work.
Start from enum declarations in your own language. Get explicit encode/decode functions, a reviewable patch and a documented wire contract in one bundle.
Prove it on your system.
Studio verifies bytes and roundtrips. It does not measure joules. Include codec work, framing and hardware behavior when measuring the net energy result.
The US Department of Energy's computing roadmap identifies data movement as an energy-efficiency challenge. This motivates the work; it is not a measurement of Studio's savings.
Watch it work
Why fewer bytes.
How to get there.
See the energy opportunity, the enum review and the code you take back to your project.
One connected workflow
Your code in.
Packed code out.
Start with code you already have.
Upload or drag in an enum-only Rust, Python or C++ source file. Parsing and code generation run locally in your browser.
Keep the meaning explicit.
Confirm the complete enum domains and review each packed code. Original enum values stay unchanged; the new wire mapping is separate.
Stay in your language.
Download modified source with a packed codec, plus the original, patch, manifest and reference vectors. No language switch or third-party runtime.
Verify the benefit.
Inspect actual bytes and benchmark layouts. Then measure total energy on your target hardware, including the cost of encoding and decoding.
Preserve the original values
Same enum.
Smaller wire code.
A state with three members needs two bits on the wire, even if its declared values are 0, 4 and 255. Studio keeps those values in your source and maps them explicitly to packed codes 0, 1 and 2.
The native example combines one state and one command. Four logical bits fit into a one-byte payload, versus two bytes for the same fields in Studio's byte-aligned layout.
Integrate the new codec at both endpoints. This does not automatically change enum memory layout or rewrite your application.
RUST / PYTHON / C++
State.Running
native value 4 → code 1Command.Stop
native value 30 → code 2Verified packed payload
09 · 1 byteTwo enum fields · two bits each · zero padding in the high four bits · no frame header included. Original enum declarations are preserved.
Small by construction
Only the bits
your values need.
Seven states need three bits. A position from zero to 1023 needs ten. Five commands need three more. Together, that is sixteen bits, with no loss of meaning.
Studio makes these choices explicit and keeps category codes stable as you work.
Explore the size comparison ↓A real 16-bit schema
2 payload bytesState3 bits
Position10 bits
Command3 bits
7 states0–10235 commands
holding · 513 · reset0a70Exact roundtrip ✓Understand the tradeoff
Smaller payloads.
The whole picture.
Compact messages can reduce storage and transfer volume. Frame overhead matters too, especially for a single record. This chart compares byte counts, not energy savings.
Drag the slider to compare the same actuator records. Then use the workspace benchmark to measure processing time on your own device.
Wire size, made visible
See where the bytes go.
64 payload bytes + 48 header bytes
128 payload bytes + 48 header bytes
Frame header Record payload
The same values, with different layouts. One frame holds 32 records. Payload: 2 bytes packed or 4 aligned per record. This is a size calculation, not a CPU benchmark.
Built for exploration
Bring a message worth understanding.
Control and telemetry
Explore bounded sensor values, actuator states and command messages with the included actuator example.
Structured state exchange
Inspect a synthetic DIS/HLA-style example. It illustrates layout choices; it is not a compliance-certified implementation.
A format you can explain
Share an exported schema and generated codec. Use project history and scoped agent access when cloud storage is configured.
Your first five minutes
Drop a file.
Build with the result.
- Sign in with your invited email address.
- Drop an enum-only .rs, .py or C++ source file, or try a built-in example.
- Review the complete domains, original values and packed codes. Approve the mapping.
- Download modified source and the bundle, then integrate and test both endpoints.
Less movement. A clearer path to integration.