Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow users to always provide input for non-uniform assemblies in the blueprints

See original GitHub issue

Currently, if the detailedAxialExpansion setting is set to False, the user input is for all the assemblies in the blueprints file are required to contain axial mesh points that are all aligned, whereas when the detailedAxialExpansion setting is set to True this restriction is lifted. It would be best if the ARMI framework allowed users to provide a mesh structure that they would like (based on the core design of each assembly) and then for the framework to handle this on reactor construction.

For instance, if we allowed any mesh to be provided when detailedAxialExpansion is set to False we could immediately call the UniformMesh converter on reactor construction before any work is performed and this would still allow a user to perform analyses using a uniform mesh.

In this case, the logic for processLoading on the reactor needs to be modified to call the UniformMesh converter if detailedAxialExpansion is set to False within the makeAxialSnapList method.

processLoading:

https://github.com/terrapower/armi/blob/0c7ef201c9f1ce5256e925b127b4a49c40659456/armi/reactor/reactors.py#L2245-L2248

makeAxialSnapList:

https://github.com/terrapower/armi/blob/0fa09f9fb43d2d1dae062f7fa89d8b2084cb0ab7/armi/reactor/assemblies.py#L575

This update will allow more flexibility for users and will also allow users to create a single blueprints file that represents the design of their reactor system. This is important for @onufer in the near term.

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

albeanthcommented, Aug 12, 2022

I think this is still an open issue. #735 was designed to address it, but opened up a hefty can of worms. It was decided to shelve that approach for now until a more formal refactor of the impacted system(s) (namely detailedAxialExpansion) can occur.

#827 aims to address this issue but needs more testing, in my opinion.

0reactions

john-sciencecommented, Aug 10, 2022

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 made some progress, what do we have left to do to complete this ticket?

Top Results From Across the Web

2.4. Settings Report — ARMI 0.2.4 documentation

Allow each assembly to expand independently of the others. Results in non-uniform axial mesh. Neutronics kernel must be able to handle.

Setting Up Input on an Actor - Unreal Engine Documentation

We would want to Enable/Disable Input based on if the player is near the light, similar to the below: Inside the StarterContent/Blueprints folder,...

Re: vRA 8.9: blueprint expression syntax for input...

I try to create a user-friendly dynamic Input inside Blueprint with vRO Action (Cloud Assembly). Array from Propiertes are OK, is sorted, but ......

Re: Will a Pro-e user ever expand to 3D Direct CAD... - PTC ...

It is certainly possible to fully control parts and assemblies parametrically in some Direct Modeling tools (CoCreate is the most capable one today)....

Virtual trial assembly of steel structure based on BIM platform

Assembly data is obtained from BIM models automatically rather than manually. ... A bare-hand interface was provided in that system to enable users...