Interaction type, formalism and consevation rules in `qrules`

[shenvitor]

See source code from qrules here

• keynotes: in the current framework of qrules: the conservation rules of strong interaction are a subset of EM, and the rules in EM interaction are a subset of weak interaction.
• strong+ EM ~ EM
• strong+ EM + weak ~ weak That means the possible resonances are the same, the difference would be for example the interaction strength. Good to recheck the correctness of the rules later in detail. p.s. more convenient to evaluate by using STM in one of the notebooks

conservation_rules

Rules	Option
MassConservation: 10,	Optional
ElectronLNConservation: 45,	W
MuonLNConservation: 44,	W
TauLNConservation: 43,	W
BaryonNumberConservation: 90,	W
StrangenessConservation: 69,	EM
CharmConservation: 70,	EM
BottomnessConservation: 68,	EM
ChargeConservation: 100,	EM
spin_conservation: 8,	canonical
spin_magnitude_conservation: 8,	helicity
parity_conservation: 6,	EM
c_parity_conservation: 5,	EM
g_parity_conservation: 3,	S
isospin_conservation: 60,	S
ls_spin_validity: 89,	canonical
helicity_conservation: 7,	helicity
parity_conservation_helicity: 4,	EM+helicity
identical_particle_symmetrization: 2,	W

formalism_node_settings.conservation_rules

"helicity"	"canonical"	"canonical-helicity"
spin_magnitude_conservation, helicity_conservation,	spin_conservation, ls_spin_validity,	clebsch_gordan_helicity_to_canonical, ls_spin_validity,

interaction_type_settings

weak_node_settings	em_node_settings	strong_node_settings
deepcopy(formalism_node_settings)	deepcopy(weak_node_settings)	deepcopy(em_edge_settings)

interaction_node_settings.conservation_rules.update

"weak_node_settings.conservation_rules.update"	"em_node_settings.conservation_rules.update"	"strong_node_settings.conservation_rules.update"
ChargeConservation(), ElectronLNConservation(), MuonLNConservation(), TauLNConservation(), BaryonNumberConservation(),identical_particle_symmetrization,	CharmConservation(),StrangenessConservation(), BottomnessConservation(), parity_conservation, c_parity_conservation,	isospin_conservation, g_parity_conservation,

[redeboer]

Beautiful 🙌 Nice job! Let's make this into a PR then: write a notebook that is essentially what you wrote in the issue description, but generate it from create_interaction_settings(), so that the rulesets are automatically updated and it serves as an integration test at the same time.

Edit: Just realized this issue is better transferred to QRules