Drew Johnson
Drew Johnson
> I would also say that the warning is not entirely justified, considering that nobody guaranteed the user that a spatial grid would be created on their block. Totally get...
> A quick review tells me that no one anywhere in the world uses this setting I think the answer is sneakier. No one turns the setting off or on...
I was working on a case w/ an EOL step and remembered this ticket. > Database3.load() takes in cycle and node as integers, thus not allowing us to load an...
Passing comment that came to me this morning: this only works if all the materials and shapes in the database are loadable, right? This change seems to - skip blueprints...
> By my count, only half the reactor projects that are currently using ARMI have assemblies. So, the above feels awkward. Imagine if there was a plugin hook called "setNumberOfHexAssemblies";...
> This is a bit orthogonal, but I have long thought that axial expansion should be moved to its own plugin. That plugin could default ship with ARMI, sure. But...
@albeanth @john-science let's talk about this offline. I'm interested but I think there's a lot of potential gotchas
Plan is going to be 1. `Block.getPinPitch` remains the same: pull `self.spatialGrid.pitch` 2. `HexBlock.getPinPitch` will not exist, instead falling back to `Block.getPinPitch` 3. But, we need a way for `HexBlock.autoCreateSpatialGrids`...
Not likely but I can be available in a pinch and/or to review