Rolling Reports – A Smarter Way to Log and Share Your CFD Results

Every CFD engineer knows that the real challenge begins after the simulation finishes – turning CFD results into something that others can understand. Copying plots into reports, building force tables, noting why a run was done and what was learned – it’s all essential, but it takes time away from what we’d rather be doing: developing the next idea.

With our latest bramble update, that changes. A few key additions to the CFD post-processing workflow make reporting and logging part of the analysis process itself — not an afterthought.

Now, instead of compiling static summaries at the end of a project, aerodynamicists and CFD teams can build live, evolving records of their work. Force breakdowns, headline metrics, design notes, and conclusions stay connected, right where the data lives, making it easier to review progress, share insights, and keep the whole development loop moving forward.

Two CFD Post-Processing Features That Change the Game

Pinned Force Tables

bramble’s CFD results view already allows engineers to create powerful, custom force tables — from headline forces to detailed drag breakdowns and mass flow reports.

Now, with the latest update, your favourite tables can be pinned. Switching between them is as simple as clicking a button. It’s quick, organised, and perfect for managing multiple types of output — whether you’re reviewing top-level metrics or diving deep into component-level analysis.

How ‘Rolling Reports’ Streamline CFD Post-Processing

By combining these tools, bramble makes it possible to create what we call a Rolling Report — a live, evolving view of your CFD project that grows as new results come in.

Rather than compiling static reports at the end of a phase, engineers and teams can now build an always-up-to-date record of their work — accessible, searchable, and fully integrated within Bramble’s collaborative environment.

A typical Rolling Report might include three tabbed views:

1. Summary – with text fields like Aim, Conclusion, and Next Steps.
2. Headline Forces – showing key performance metrics.
3. Force Breakdown – a deeper dive into drag, lift, and balance by component.

Together, these views tell the complete story of a project — what was tested, what was found, and where to go next.

Reporting, Evolved

With Bramble’s refreshed interface, engineers can now move seamlessly from running simulations to reporting their findings — all in one place.

No more copy-paste reports. No more digging through folders for screenshots or tables. Just live, logged, shareable results that evolve with your development process.

Related articles