Skip to content
Mehmet Eren DereliMACHINE / MARKDOWNTR
Open raw Markdown

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 SOURCE / ENGINEERING EVIDENCE

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

Open GitHub profile

Inspect VORMETRA Slice

  • 2: active public projects
  • AGPL/MIT: open-license models
  • CLI/API/MCP: inspectable interfaces

VORMETRA Slice

01 / SLICING AND CONTROL

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 source

Open the control source

Open passing CI run

Inspect it locally

git clone https://github.com/mehmeterendereli/vormetra-slice.git

Software output path

3D MODEL → C++ SLICER → G1000 PROFILE → G-CODE → LINUXCNC

Programmatic control path

CLIENT → MCP · HTTP → VERA CONTROL → SLICER CLI

OpenRelax PC Care

02 / FOCUSED UTILITY

SINGLE-SCRIPT WINDOWS UTILITY

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 source

Open Windows CI run

For a read-only inspection

powershell -NoProfile -ExecutionPolicy Bypass -File .\openrelax.ps1 -SelfTest

Execution flow

  1. SELECT
  2. SELF-TEST
  3. BACKGROUND
  4. REPORT

Trace the implementation decisions.

WORKING STANDARD

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.

Working on an integration, machine or production problem?

FROM CODE TO PRODUCT

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

Discuss the project

All public repositories

Sources