Multipath Dual Object Properties

Description

This process involves copying essential properties from an original Radar object (either a Transmitter or Receiver) to its newly created "dual" object, which represents the radar's image for multipath simulation. Key properties copied typically include the associated Antenna, Timing source, PRF settings, Signal definition, noise temperature settings, and window configuration parameters (for Receivers). Additionally, this step sets a multipath flag and the reflection factor (power loss/gain multiplier associated with the reflection) on the dual object using the setMultipathDual method.

Assumptions

• Assumes that the specific set of properties copied within the createMultipathDualBase template function is sufficient and complete for the dual object to function correctly within the simulation.
• Assumes the _multipath_factor provided by the MultipathSurface and set on the dual object correctly represents the desired power scaling (typically loss) associated with the signal reflection.

Limitations

• Manual Property Copying: The mechanism relies on manually coded copying of specific properties within the createMultipathDualBase template function. If new, relevant properties are added to the Radar, Transmitter, or Receiver classes in the future, this template function must be explicitly updated to copy them to the dual object.
• Reflection Factor Warning Only: While the Radar::setMultipathDual method logs a warning if the provided reflection factor (_multipath_factor) is greater than 1.0 (which would imply gain from the reflection), it does not prevent this value from being set or used in subsequent calculations.

Related Components

• `radar_obj.cpp::createMultipathDualBase<T>` (Template function performing the copy)
• `radar_obj.cpp::Radar::setMultipathDual` (Method setting the factor and flag)
• Radar, Transmitter, Receiver classes (Objects being copied)
• Multipath Image Object Generation (Process that calls createMultipathDualBase)
• MultipathSurface class (Provides the reflection factor)
• Antenna, Timing, Signal classes (Examples of properties being copied/referenced)

Validation Status

• Needs Verification: Confirmation that all currently necessary properties are correctly copied for both Transmitter and Receiver duals. Verification of the exact conditions under which the factor > 1 warning is logged.
• Key Areas for Validation:
  • Compare property values between original and dual objects after creation for various configurations (Tx, Rx, Monostatic).
  • Verify that no essential properties for simulation physics or output generation are missed during the copy.
  • Test setting a reflection factor > 1.0 and confirm the warning is logged correctly to stderr or the configured log file.
  • Investigate downstream effects (if any) of setting factor > 1.0 (does it simply scale power, or cause issues?).
• Priority: Medium (Essential for correct multipath simulation, but relies on the more fundamental geometric reflection being correct first).