Skip to content

MF26 multiplicity should always be 1 #168

Description

@whaeck

The ENDF manual says that the multiplicities must always be 1, not just "normally one". Thus, it doesn't really make sense to require it as an input. I think the only value of this constructor would be to make a user specify the energy range and the law.

That said, maybe consistency with MF6 is desired? So maybe this is okay?

Originally posted by @nathangibson14 in #143 (comment)

Verify if this is the case and add a check to verify this, also see about simplifying the constructor as a result of this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions