John Stilley

Well, I don't have a fully-formed thought on this yet. One thing I will note right now is `Block.breakFuelComponentsIntoIndividuals()` has been in ARMI for 3-5 years now, so it's certainly...

@albeanth @jakehader - Thoughts?

What's the status of this, after your recent `copyInterfaceInputs()` PR?

@jakehader @scottyak My preference is to only support Python 3.7-3.9, as those are really the only versions that we test for seriously. And while I'm generally a fan of supporting...

@jakehader @scottyak It looks like no one is using Python 3.6 anyway. Nick is hesitant to drop support for 3.10, so I _think_ saying we support Python 3.7+ is a...

How far have our recent PR go to solving this Issue? #735 - Process load update and new uniform mesher #827 - Support non-uniform assemblies with detailedAxialExpansion disabled If we...

I wouldn't mind moving the GUI to a static JavaScript web browser tool. We could keep the current workflow, where it is spawned via the same commandline, and it doesn't...

@scottyak Yes, the switch to a browser-based solution would be a complete re-write. That's definitely the down-side. I am just looking at this "test the GUI" PR that's been open...

> We are considering adding [NotebookJS (MIT license)](https://github.com/jorgehpo/notebookJS) as a dependency. You're right that it's a very small project. But I like that it is well documented. It has an...

> armi.materials.setMaterialNamespaceOrder(['armi.materials', 'userMaterial']) I'm not sure this is such a bad solution, really. We can't store _code_ in the database. And if you want to define a custom material with...