MatForge — Open Knowledge Hub for Scientific Simulation and Modeling

Reading Time: 6 minutesScientific transparency is often discussed in terms of final outputs: published papers, shared datasets, open-source code, and archived results. These are important, but they do not always show how a research team reached a decision. A paper may explain the final method, while the project history may contain unresolved questions, bug reports, model assumptions, failed […]

Reading Time: 7 minutesFiPy is often used in research workflows where small software changes can matter. A new release may include documentation updates, dependency adjustments, solver-related fixes, examples, performance notes, or changes that affect how a simulation is configured. For casual experimentation, these updates may seem minor. For published research, teaching material, or long-running modeling projects, they can […]

Reading Time: 5 minutesModern science is often remembered through a familiar script: a problem becomes visible, an instrument captures something new, and a discovery enters public memory as a breakthrough. That script still matters, but it no longer explains enough. In many fields, the decisive shift did not come from a microscope, a telescope, or a single dramatic […]

Reading Time: 10 minutesPerformance optimization for Python PDE solvers follows a simple rule: profile first, optimize later. Use tools like cProfile and line_profiler to identify actual bottlenecks—typically sparse matrix operations, memory allocation, or algorithmic complexity—before applying targeted fixes. Common gains come from: choosing optimal sparse matrix formats (CSR for reads, CSC for writes), leveraging Numba JIT for tight […]

Reading Time: 11 minutesContinuous Integration (CI) automatically builds, tests, and validates research code on every commit. For scientific software, CI is essential for reproducibility, early bug detection, and maintaining quality over time. Implement CI by: (1) writing automated tests with pytest, (2) setting up a CI pipeline using GitHub Actions or GitLab CI, (3) using Docker/Conda for environment […]

Reading Time: 7 minutesIn many teams, issue resolution is treated as a technical finish line. A bug is fixed, a service is restored, an alert stops firing, and the ticket is closed. From an operational point of view, that may look like success. But if the knowledge gained during the incident disappears as soon as the system is […]

Reading Time: 8 minutesFiPy is most useful when you stop treating it as a collection of isolated example scripts and start using it as a flexible framework for building your own PDE workflows. That shift matters because real simulation projects rarely stay simple for long. A model that begins as one equation on one mesh often grows into […]

Reading Time: 7 minutesDevelopers often learn performance from small examples: a faster loop, a cleaner benchmark, a language comparison, a clever micro-optimization. Those examples are useful, but they can also hide the harder truth. Real performance work is rarely about finding one “fast trick.” It is about understanding how a workload behaves when data grows, when memory becomes […]

Reading Time: 10 minutesTL;DR In-situ visualization processes and analyzes simulation data while the simulation runs, directly in memory, instead of writing raw results to disk for later post-processing. This approach is essential for exascale computing where I/O bandwidth cannot keep up with data generation. By integrating visualization during computation, you can: Avoid I/O bottlenecks that cripple traditional workflows […]

Reading Time: 8 minutesLearn how to simulate soft tissue deformation and cardiovascular blood flow using PDEs. Compare FEM vs FVM, implement with FiPy, and apply validation best practices.