Magic functions should handle different fields... differently

[JSahliCU]

• Add/subtract/multiply/divide: when you add two data arrays together that contain fields, that's fine. Adding fields is okay. When you add the directivities/gains/axial ratios/etc, we get a nonphysical answer. So we should recompute directivity/gain/etc when we add two data arrays together

[TheoPrinceColorado]

there should probably be some option to not recompute farfield quantities like directivity/gain/etc, and just have the operation add fields. I'm thinking this could be useful for arrays.

Ex: we have an antenna array with 1000 elements. We want to compute 100 different beams from said array. Its faster to do a single computation of directivity AFTER summing the fields for each beam (100 ff calculations), rather than computing ff quantities after each addition of fields (1000*100 ff calculations).

Maybe the way to do this is to have the add/subtract compute ONLY the quantities present in both pattern objects.

Ex: pattern1 and pattern2 contain only electric fields. pattern1+pattern2 = pattern3. patterns 1 & 2 contain only electric fields, so we only need to add the fields together. NOW if pattern3 and pattern4 contain electric fields AND directivity AND we add them together, we must add the fields then recompute directivity.

This means we also need to give the user to compute any FF quantity they want from the pattern object! Like directivity, axial ratio, gain, etc.