Modelica good first issues

The user has identified a potential FMI compliance issue with JModelica's Windows FMUs, where backslashes ('\') are used instead of forward slashes ('/') in file paths. This prevents the FMUs from passing FMI standard tests, although they function correctly in Python environments. The user is inquiring if this is an easy fix.

This issue discusses the trade-off between manually optimizing algorithms for numerical efficiency in Modelica.Math versus relying on AI. The author provides an example of a Newton-Cotes quadrature function and an alternative implementation, claiming the alternative is more efficient. They are seeking input from tool vendors and experts on this optimization strategy.

The user is requesting an enhancement to the `quadratureLobatto` function in the Math library. They need to pass additional parameters to the partial scalar function being integrated, as the current implementation only supports functions with a single input and output.

This issue proposes organizing external resources for test cases within their respective Modelica packages. The goal is to move resources like weather and occupancy data from a general 'Resources' folder to a dedicated 'Resources' subfolder within each test case package, and then remove them from the original location.

Investigate why the 'peak_heating_day' scenario for the twozone apartment hydronic testcase in the BOPTEST framework initializes with an infeasible temperature, causing initial thermal discomfort. Determine if this is intentional or a bug in the baseline control, and suggest a fix to ensure fair comparison between different controllers.