Add Relative wind offset to IPF

[MrD-RC]

User description

Added Relative wind offset which gives the relative difference in degrees between the wind heading and aircraft heading. 0 degrees is flying directly in to the headwind. -180 to 1 degree(s) signifies a counter-clockwise offset.

---

PR Type

Enhancement

---

Description

• Added "Relative Wind Offset [deg]" operand type to IPF

• Provides relative difference in degrees between wind and aircraft heading

• 0 degrees indicates flying directly into headwind

• Negative values (-180 to -1) signify counter-clockwise offset

---

Diagram Walkthrough

flowchart LR
  A["IPF Logic Conditions"] -- "adds new operand type" --> B["Relative Wind Offset [deg]"]
  B -- "calculates" --> C["Wind vs Aircraft Heading Difference"]

Loading

File Walkthrough

	Relevant files
Enhancement	logicConditionOperantTypes.js Add Relative Wind Offset operand type entry                            js/logicConditionOperantTypes.js Added new operand type entry 49 for "Relative Wind Offset [deg]" Inserted into OPERAND_TYPES object under appropriate section Maintains existing operand type numbering and structure +1/-0

---

[qodo-code-review]

PR Compliance Guide 🔍

(Compliance updated until commit 18cb43a)

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: No auditing: The added operand type is a label addition with no logging or auditing changes, so it neither implements nor violates audit trail requirements based on the visible diff. Referred Code 49: "Relative Wind Offset [deg]", } Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: No error paths: The change is a static mapping addition and introduces no executable logic or error paths to assess for error handling. Referred Code 49: "Relative Wind Offset [deg]", } Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: No inputs touched: The change adds a constant label and does not introduce new inputs or data handling to validate in the visible diff. Referred Code 49: "Relative Wind Offset [deg]", } Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

---

Previous compliance checks

Compliance check up to commit 18cb43a

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: No audit context: The added mapping for Relative Wind Offset [deg] does not include or reference any logging of critical actions, so it is unclear if related read/write operations are audited elsewhere. Referred Code 49: "Relative Wind Offset [deg]", } Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: No error handling: The change only adds a new operand type label without visible validation or error handling for invalid/unknown operand IDs, leaving robustness unclear. Referred Code 49: "Relative Wind Offset [deg]", } Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Validation unknown: Adding a new operand mapping does not show whether external inputs referencing operand 49 are validated or sanitized, so security posture cannot be confirmed from this diff. Referred Code 49: "Relative Wind Offset [deg]", } Learn more about managing compliance generic rules or creating your own custom rules

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.