Skip to content
Mehmet Eren DereliManufacturing • Design • AI-Assisted Software
Get in TouchTR

OPEN SOURCE / ENGINEERING EVIDENCE

Source code, implementation and test records.

Explore the problems, implementation decisions and verification records behind two open-source projects, with direct links to code, tests and CI runs.

Open GitHub profileInspect VORMETRA Slice
2
active public projects
AGPL/MIT
open-license models
CLI/API/MCP
inspectable interfaces

01 / SLICING AND CONTROL

VORMETRA Slice

ACTIVE DEVELOPMENT

Slicing and programmatic control for a large-format pellet/FGF manufacturing chain.

Engine + profiles: AGPLv3 · vera-control: MIT

The goal is to drive slicing from local software and agent workflows. G1000 profiles and the Python vera-control layer extend the upstream OrcaSlicer C++ engine with model preflight, process management and result parsing through HTTP, MCP and Python interfaces.

Implementation and verification

  • G1000 profile: a recorded real CLI run produced 50 layers from a 200 × 200 × 100 mm model
  • Model-size and invalid-input checks; tests for timeout errors and releasing the job lock
  • Corrupt/stale-lock recovery; local HTTP tests for foreign Origin/Host rejection and busy-job 409 responses
  • Windows/Ubuntu × Python 3.10/3.13: all 4 CI jobs passed; the linked Windows log records 31 passed and 3 skipped tests

CI skips real-slicer and optional LinuxCNC-converter tests when their local dependencies are absent. The digital slicing record does not verify a physical print; uncalibrated profile values are marked separately.

Inspect the sourceOpen the control sourceOpen passing CI run
Inspect it locallygit clone https://github.com/mehmeterendereli/vormetra-slice.git

Software output path

  1. 3D MODEL
  2. C++ SLICER
  3. G1000 PROFILE
  4. G-CODE
  5. LINUXCNC

Programmatic control path

  1. CLIENT
  2. MCP · HTTP
  3. VERA CONTROL
  4. SLICER CLI

02 / FOCUSED UTILITY

SINGLE-SCRIPT WINDOWS UTILITY

OpenRelax PC Care

A no-install Windows maintenance utility built with PowerShell and WinForms, with explicit safety boundaries.

The goal is to make maintenance targets and changes visible to the user. Cleanup categories, privilege checks, a background runspace and read-only -SelfTest mode have separate responsibilities within one PowerShell application.

  • Windows CI passed the PowerShell parser check and a real -SelfTest application process
  • Before/after file fingerprints confirmed that settings and the AutoClean log stayed unchanged
  • Contract tests simulated service-stop failure and checked cleanup blocking plus restoration of prior service states
  • Prefetch, browser profiles/history and diagnostic logs are excluded from cleanup targets

MIT · PowerShell · Windows Forms

Inspect the sourceOpen Windows CI run
For a read-only inspectionpowershell -NoProfile -ExecutionPolicy Bypass -File .\openrelax.ps1 -SelfTest

Execution flow

  1. 01SELECT
  2. 02SELF-TEST
  3. 03BACKGROUND
  4. 04REPORT

WORKING STANDARD

Trace the implementation decisions.

Source, tests and execution records together make a project’s current scope easier to assess.

01

Inspectable architecture

Components, interfaces and dependency boundaries should be visible in the repository.

02

Reproducible start

Clone, run and test commands should be directly available.

03

Safety boundaries

What a system refuses to do, and when it stops, matters as much as features.

04

Honest maturity

Prototype, active development and production evidence must not be blurred together.

FROM CODE TO PRODUCT

Working on an integration, machine or production problem?

We can consider the requirements, implementation boundaries and verification steps together.

Discuss the projectAll public repositories