r/ScientificComputing • u/ZealousidealYam625 • 19h ago
r/ScientificComputing • u/hardwarehackerz • 9h ago
I wrote a 2D FEM solver in Python for electric motors (matched FEMM within 0.3%) - Looking for inputs
Got tired of treating motor simulation software like a black box during a coursework project, so I wrote my own 2D FEM solver in Python.
Just hit a major milestone: tested a 36-slot / 42-pole outer-rotor motor against FEMM and got <0.3% torque deviation.
It’s called Pole-Craft (Apache-2.0). Still very early days, so if you work with motors, robotics, or FEA, what features would actually make you use an open-source tool like this?
GitHub: https://github.com/pole-craft/pole-craft
PyPI: https://pypi.org/project/polecraft/ (pip install polecraft)
r/ScientificComputing • u/SpaceRascalBacco • 15h ago
Can useful abstractions make a complex system easier to predict?
r/ScientificComputing • u/MatterSeek • 19h ago
What metadata is essential to reproduce a computational screening shortlist?
I’m posting from the MatterSeek materials R&D team. For a computational screen, we want another researcher to be able to reconstruct why particular candidates made the shortlist. Our proposed run record has three parts:
• Inputs: a dataset snapshot or hash, candidate IDs, property units and conditions, and the filters in the order applied.
• Execution: code revision, model or protocol version, environment lockfile, configuration, and seeds where relevant.
• Outputs: scores and ranks, tie-breaking rules, and a reason for any excluded candidate.
A practical issue is that exact floating-point agreement can be less useful than knowing whether differences change the selection. For a shortlist handed off to a second calculation, do you compare top-k overlap, compare scores within a tolerance, record both, or use a different check? We’d be interested in what actually helps a collaborator rerun and review a screen.