Use EnergyPlus Python API instead of MLEP

[anyaelena]

From 4/18 meeting:

Notes:

• the Python API is implemented as callbacks from sim manager running within E+ so a out callback functions will need to be designed to hijack timing of advance.

Advantages:

• Directly get values in EMS namespace
• Retire MLEP and use of External Interface
• Alfalfa gem code becomes less complicated -> better developer support for workers
• Workers will no longer have Java dependency
• Make Alfalfa runs more stable than local runs?
• Easier to have support from E+ team

Disadvantages

• Time and attention
• Do we need to rewrite measures?? (if yes, that actually adds urgency to migration)

[anyaelena]

@TShapinsky is scoping the effort involved.

[anyaelena]

this coordinates with #478

[TShapinsky]

pyenergyplus is packages with E+. So to use it we will need to add it from E+ to the python path. The most recent version of E+ doesn't have a OS release yet, but I think there's an RC.

[anyaelena]

Need to coordinate with E+, OS releases. Need latest E+ and OS release lags these. Then need time for Alfalfa release. Earliest release would be FY25Q1, more likely FY25Q2. Related to #506 in that we would like to coordinate the rework happening in worker

this change introduces breaking changes in some measure functions but these are not yet widely used