You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it odd that XS groups in this setting are referred to by their type+burnup group (i.e. GA as compared to just G)? Here are a few potential points of confusion:
The user might look through their blueprints and see that XS type GA is not defined for any blocks, for instance. This is confusing.
It might make one think that the setting is referring to only the first burnup group of a given XS type, in which case the later burnup groups of that type would fall back to the default.
Is the driverID: AA referring to the first burnup group of XS type A, or generically all of group A, or the 2-digit group AA? Is this driver group updated with burnup somehow?
It doesn't help that the crossSectionControl setting is hardly mentioned in the user docs.
I would suggest clarifying these few points, primarily by adding thorough documentation of the crossSectionControl setting, but also potentially by updating the way XS groups are specified within the setting itself.
The text was updated successfully, but these errors were encountered:
A typical example of using the
crossSectionControl
setting might look something like this:Is it odd that XS groups in this setting are referred to by their type+burnup group (i.e.
GA
as compared to justG
)? Here are a few potential points of confusion:GA
is not defined for any blocks, for instance. This is confusing.driverID: AA
referring to the first burnup group of XS typeA
, or generically all of groupA
, or the 2-digit groupAA
? Is this driver group updated with burnup somehow?It doesn't help that the
crossSectionControl
setting is hardly mentioned in the user docs.I would suggest clarifying these few points, primarily by adding thorough documentation of the
crossSectionControl
setting, but also potentially by updating the way XS groups are specified within the setting itself.The text was updated successfully, but these errors were encountered: