01
Private workspace
Raw experiments, controller prototypes, simulation, notes, storage connections and AI-assisted drafting stay behind authentication.
Behind the public portfolio
A research workspace I actually use.
The website is not only a place where I publish finished work. The private side is where experiments are collected, controllers are tested, flight data is replayed, references are synchronized and public updates are prepared.
I made this page because I enjoy seeing how other researchers organize their own work. It is a personal workflow note, not a product or a template.
MMPrivate workspace
Research command center
Ciao Mirko.
archive
Experiments
active
Projects
sync
Publications
AI brief
Arena
Quick actions
Import flight
Run simulation
Draft update
The idea
One research loop, two surfaces.
02
Public portfolio
Only material I decide to expose becomes part of the public site: research areas, publications, updates, CV and selected platform material.
How I use it
From a flight in the lab to something worth publishing.
01
Capture
Import a flight log or experiment package and keep the processed data linked to its project.
02
Inspect
Replay the miniThex in 3D, inspect trajectories, switching, rotor speeds, wrench and tracking errors.
03
Test
Use the Arena to run the same control ideas on a virtual rigid-body model before returning to the platform.
04
Publish selectively
Turn only the useful result into a publication entry, research update, CV item or public explanation.
Virtual Arena
The same lab view, with the platform itself as a choice.
This public preview reads the platform visibility selected inside my private Arena. The simulator and controller work remain private; the models shown here are the ones I choose to expose.
Loading selected research platforms…
The controller, body-wrench interface, platform allocation and plant remain separate layers. miniThex keeps the full FA/UA workflow; the quadrotor uses the DFL profile fixed in underactuated mode; the propeller pendulum is already part of the platform library while its controller is still intentionally under development.
AI as an assistant, not the workflow
I use AI inside the private side for bounded tasks: polishing a research update, summarizing activity, or drafting a controller script that I review before it enters the controller library.
DraftGenerate or improve a first version.
ReviewNothing generated becomes active automatically.
PublishPublic material is still an explicit decision.
Why keep it visible?
Research is also the system around the research.
The papers remain the important output. But the way experiments, code, models, notes and communication are connected determines how easy it is to revisit an idea months later. This private workspace is my attempt to make that part less fragmented.