A new air to water heat pump object #11001

yujiex · 2025-03-20T23:53:12Z

Pull request overview

Description of the purpose of this PR

Heat pumps are an essential technology for decarbonizing buildings. EnergyPlus is capable of modeling several types of heat pumps, e.g., for space cooling or heating: air to air, air to water, water to water; and heat pump water heaters. Although there is an existing feature to model air-to-water heat pumps in EnergyPlus, its capability is limited and its implementation is not straightforward compared with other types of HP. Some of the limitations include:

Cannot specify parameters like single, multi-speed, or variable speed for capacity control (for example, the Daikin model EWYT-CZ series is inverter controlled, and the EWYQ series is a fixed-speed two-stage model.)
Missing details of crankcase heater control and more flexible defrost control
The naming of the object is not intuitive - it does not refer to water to water or air to water, making searching for the object difficult
Missing the input of an availability schedule (which disables the HP for seasonal consideration)
Designed as separate heating and cooling objects while in reality, it should be one piece of equipment

This feature will create a new air-to-water heat pump (AWHP) model that includes heating and cooling components in one single object, capable of multi-speed controls, and includes more equipment details such as fan characteristics, PLR ranges, availability schedules, etc.

About the extended internal data structure arrays

The following entried are added to the internal data structure to hold info about this new AWHP.

Entries Added to

HeatPumpAirToWaterCooling,
HeatPumpAirToWaterHeating,
HeatPumpAirToWater, “ConnectionObjectType” in DataLoopNodes.hh
“PlantEquipmentType” in Enums.hh

"HeatPump:AirToWater:Cooling",
"HeatPump:AirToWater:Heating",
"HeatPump:AirToWater", PlantEquipTypeNames in DataPlant.hh
“ConnectionObjectTypeNames” in BranchNodeConnections.cc

"HEATPUMP:AIRTOWATER:COOLING",
"HEATPUMP:AIRTOWATER:HEATING",
"HEATPUMP:AIRTOWATER", “PlantEquipTypeNamesUC” in DataPlant.hh
“ConnectionObjectTypeNamesUC” in BranchNodeConnections.cc

Regression diffs

798 files have regression diffs
Select a representative one, for example, 5ZoneAirCooled, the diffs happen in

audit: the number of SubTable and ColumnTags are different, due to the addition of HTML output table "AWHPs" in the equipment summary and the added entries in the "central plant" table

tbl diff: it shows up as diff in the summary but the diff file shows 0 diff

Pull Request Author

Reviewer

EnergyArchmage · 2025-03-21T14:54:48Z

As I read the description it sounds like you intend one set of plant nodes for cooling loop connection and another set of plant nodes for heating loop connectiong. But the IDD only has one set.

yujiex · 2025-03-21T17:36:13Z

As I read the description it sounds like you intend one set of plant nodes for cooling loop connection and another set of plant nodes for heating loop connectiong. But the IDD only has one set.

I was debating on this: whether I should do separate sets of nodes for heating, cooling, and potentially domestic hot water; or resemble the actual system which just have one set of nodes (1 air 1 water). Any suggestions?

JasonGlazer · 2025-03-24T12:18:14Z

design/FY2025/NFP-new-air-water-heat-pump.md

+
+Table 2. Input fields of the heat pump objects in EnergyPlus
+
+<table class="table table-bordered table-hover table-condensed">


This table is almost impossible to read on GitHub since the columns are so wide and it is so tall it cannot be scrolled. I would suggest either breaking it into multiple tables or make the column width narrower by using shorter titles in each.

let me adjust the format and try to make it more readable

I reformatted the table. Hope it's more readable now.

JasonGlazer · 2025-03-24T12:23:31Z

design/FY2025/NFP-new-air-water-heat-pump.md

+## Proposed Approach ##
+
+This new feature proposes to create a new input object, HeatPump:AirToWater.
+


It is very difficult to compare what is being proposed to what appeared in the table of existing heat pumps because the of difficulties in that table (see previous comment). Perhaps repeat the table with the new object or else include it in the original table. Or perhaps you state that you are including all features from that table (if you are).

I will include the proposed one in the comparison table.

The proposed object is added as another row in the idd comparison table

JasonGlazer · 2025-03-24T12:25:44Z

design/FY2025/NFP-new-air-water-heat-pump.md

+- time since defrost started, timeSinceStart
+
+Note that ambient air temperature is already an existing EnergyPlus actuator. It could be used in defrost calculation as well.
+


Please describe the outputs that you are planning to provide. Including timestep output variables, modifications or additions to the tabular outputs, and whether any rated efficiency metrics (such as from AHRI or ISO or other standards organizations) are going to be provided.

I will add a section describing the output

I added a section listing the output variables

Thanks. It would be great to add a tabular output file in the Equipment Summary report. Maybe it could include outputting a calculated rating efficiency equivalent to an AHRI or ISO test procedure (assuming there is one).

Thanks! Just added some contents to the "Outputs" section including some info on entries to be added to the Equipment Summary report.

JasonGlazer · 2025-03-24T12:28:10Z

design/FY2025/NFP-new-air-water-heat-pump.md

+boiler to produce hot water. The following is an example of the current object.
+The object specifies capacity and EIR as functions of temperature and part load
+ratio, with three performance curves.
+


Is this new object intending to replace the use of any existing objects and deprecate those? If not, adding a new object just seems to add some additional confusion on which one should be used. Perhaps you should include in the NFP some user oriented guidance on when each object that is mentioned in the NFP should be used including the proposed new one.

The new object can model multi-speed/variable-speed/modular products while the existing one can't. So for these cases users would want to use the new object. I will add some documentation on how to choose between them.

I added a section with notes on which model to use to model an air-to-water heat pump.

yujiex · 2025-04-08T00:09:00Z

Thanks for the feedbacks from the last technicality meetings. Regarding the few issues brought up.

The idd object is modified to have separate water inlet outlet nodes for chilled water loop, hot water loop, and condenser loop.
We will try to reuse existing logic/code but we're leaning towards keeping the new object with the heating and cooling component both encapsulated in this object. The new object will manage the coordination of heating and cooling operation internally.
As for the performance curve: the 205 chiller performance map option is indeed pretty generic and clean. However manufacturers do not have this kind of data, they seem to provide data by stage (or speed level for variable-speed case). The current plant loop heat pump object performance curves cannot fully represent multi-stage products. The following is a toy example.

Toy example

For simplicity, we'll control theControl PLR to be the same: PLR = 0.4 (load / max capacity = 0.4)
Capacity is a function of both air and water temperature, for easy display, we'll fix the air temperature and only vary the water temperature. The figure plots the low-capacity and high-capacity heating capacity data

As the plant loop heat pump only has one EIR curve as a function of air and water temperature, and EIR curve as a function of PLR, we want to find a PLR adjustment function f(.) such that the following holds.

$$ EIR_{high}(T_{air},T_{water}) * f(PLR) = EIR_{low}(T_{air},T_{water}) $$

As PLR is fixed to 0.4, $f(PLR)$ should be a constant, however, from the following EIR data plot. The $EIR_{high}(T_{air},T_{water}) / EIR_{low}(T_{air},T_{water})$ ratio are different for different water temperature value. We cannot find an $f(0.4)$ to make the above equation holds.

For heating capacity, the one set of curve is also not enough: Using just one set of curve, the cycling ratio is always 0.4 (for simplicity assuming there's no minPLR limits and cycling ratio and PLR are equal) in this example for all water temperature values shown in the first figure. However, in reality, the second stage compressor will always be off and the first stage compressor will cycle. It's cycling ratio is not always constant, it varies between 0.73 and 0.75.

yujiex · 2025-04-14T22:45:06Z

Re @EnergyArchmage question from last time, we have a field "Compressor Multiplier" to model modular heat pumps where several of the same AWHP objects can be used together to provide larger heating/cooling capacity.

We will restrict the system to allow only one Air-to-Water Heat Pump (AWHP) object to serve a single hot or chilled water loop. This means that load splitting between two AWHP objects will not be permitted. The current object cannot model scenarios where two multi-stage AWHPs (AWHP-A with "Compressor Multiplier" = 2) and one variable speed compressor AWHP (AWHP-B with "Compressor Multiplier" = 1) serve the same set of heating or cooling loads, as this would require splitting loads between the two AWHPs, which is not allowed.

However, we do allow configurations where one AWHP serves the first floor and another serves the second floor, with each floor having its own dedicated plant loop.

rraustad · 2025-09-29T21:11:39Z

The speeds are now reported discretely for FixedSpeed, I haven't tested VariableSpeed ControlType yet. Do you consider adding additional output variables like Cycling Ratio or Speed Ratio to report the ratio between stages, like UnitarySystem?

Re 2: There is a cycling ratio to capture the case for when the capacity at minimum speed level is larger than the demand. Would we want a speed ratio output for the demand > min-speed-capacity @dareumnam?

@yujiex I think the output (a speed ratio output for the demand > min-speed-capacity ) will definitely be helpful to the modelers, so it’s a good idea to include it as well. @mitchute do you have any other thoughts on this?

SpeedRatio is used for multi- or variable-speed components (e.g., the 10-speed coil model). PartLoadRatio is used for single-speed units with a cycling ratio variable to show when the unit turns on and off in a time step. You can certainly add SpeedRatio but it should be the same as PartLoadRatio so would be redundant at speed 1.

Update: This new model does have a Number of Speeds input so maybe this is a good idea.

yujiex · 2025-09-29T21:18:34Z

@dareumnam @rraustad thanks for your input. I will add a speed ratio output.

github-actions · 2025-09-30T00:37:57Z

⚠️ Regressions detected on macos-14 for commit `0f601d3`

Regression Summary

Audit: 798
Table Big Diffs: 2

github-actions · 2025-09-30T00:41:45Z

⚠️ Regressions detected on ubuntu-24.04 for commit `0f601d3`

Regression Summary

Audit: 802
Table Big Diffs: 2

rraustad · 2025-09-30T01:24:39Z

src/EnergyPlus/PlantLoopHeatPumpEIR.cc

+            this->eirFuncTempCurveValue = (1 - interpRatio) * eirModifierFuncTempLow + interpRatio * eirModifierFuncTempHigh;
+            this->eirFuncPLRModifierValue = (1 - interpRatio) * eirModifierFuncPLRLow + interpRatio * eirModifierFuncPLRHigh;
+        }
+    }


@yujiex do you think you need to pull the powerUsage at lines 702 and 703 into this if/else block? why set speed level and performance curves at the high speed for CompressorControlType::FixedSpeed and interpolated otherwise while the power calculation always interpolates?

for the multi-stage fixed-speed case, when the demand is between speed level n and speed level n-1, the heat pump runs p% time at speed n and (1-p)% time at speed n - 1.
for the variable speed case, it interpolates the performance curve to mimic modulating to a intermediate speed to satisfy the demand

I felt the two should theoretically result in the same power consumption? Like if the two speed level has capacity 100W and 200W and that the demand is 150W for example, then in the first case, it will have 50% time running at the lower speed and 50% time running at the higher speed; in the second case, it will interpolate the two speed levels with interpolation factor of 0.5. In both cases, they'll have the same power consumption: average of the power at the two speed level?

rraustad · 2025-09-30T01:35:09Z

src/EnergyPlus/PlantLoopHeatPumpEIR.cc

    // currentLoad will be met and there should? be some adjustment based on outlet water temp limit?
 }

+void HeatPumpAirToWater::calcLoadSideHeatTransfer(EnergyPlusData &state, Real64 const availableCapacity, Real64 const currentLoad)


This may be out or scope for this new model but all plant equipment models should be passing back the load met (Real64 &currentLoad) to the plant manager (i.e., returned from the simulate function call to the plant manager) so the plant knows what the remaining load is. If the load is greater than the equipment capacity then the plant will have a remaining load to meet. All the simulate functions should look like this: simulate(state, , , Real64 &curLoad) {}

I see. Although in void EIRPlantLoopHeatPump::simulate(), it seems like CurLoad is not updated in the function: in in both setOperatingFlowRatesASHP(..., CurLoad), and doPhysics(state, CurLoad), CurLoad is passed by value.

rraustad · 2025-09-30T12:22:55Z

src/EnergyPlus/PlantLoopHeatPumpEIR.cc

+    // calculate power usage from EIR curves
+    Real64 eirModifierFuncTempLow = 1.0;
+    Real64 eirModifierFuncPLRLow = 1.0;
+    if (speedLevel > 0) {


I noticed at the bottom of this function is this->speedLevel += 1; and that this conditional and the curve indexes below use a local variable speedLevel. This local variable is always = the operating speed. So what does the this->speedLevel += 1; at the bottom of the function do?

this->speedLevel += 1 is for reporting. In the internal calculation, the speed level is 0-indexed. But to follow the reporting convention, speed level need to start from 1. So there is the shift in this->speedLevel.

github-actions · 2025-09-30T18:08:11Z

⚠️ Regressions detected on macos-14 for commit `7af3821`

Regression Summary

Audit: 798
Table Big Diffs: 2

github-actions · 2025-09-30T18:20:51Z

⚠️ Regressions detected on ubuntu-24.04 for commit `7af3821`

Regression Summary

Audit: 802
Table Big Diffs: 2

rraustad

All questions were sufficiently answered. @mitchute this looks ready.

mitchute · 2025-10-01T00:51:18Z

I bumped the version numbers up to current. We can merge this after CI wraps up one last time.

github-actions · 2025-10-01T01:42:16Z

⚠️ Regressions detected on macos-14 for commit `434addf`

Regression Summary

Audit: 798
Table Big Diffs: 2

github-actions · 2025-10-01T01:55:09Z

⚠️ Regressions detected on ubuntu-24.04 for commit `434addf`

Regression Summary

Audit: 802
Table Big Diffs: 2

dareumnam

@rraustad, thanks so much for your review and input.
I built it locally, ran the newly added unit tests (all passed), and ran the created test files successfully, confirming the results match what Yujie explained. CI checks look good, diffs are explained and verified, comments have been addressed, and all related documentation has been updated. This one looks all set to go. @mitchute

mitchute · 2025-10-01T16:10:27Z

OK, I made another quick review and made one final commit. We'll let CI finish, then merge this.

github-actions · 2025-10-01T16:35:06Z

⚠️ Regressions detected on ubuntu-24.04 for commit `7ab7c32`

Regression Summary

Audit: 802
RDD: 3
Table Big Diffs: 2

github-actions · 2025-10-01T16:37:28Z

⚠️ Regressions detected on macos-14 for commit `7ab7c32`

Regression Summary

Audit: 798
RDD: 3
Table Big Diffs: 2

mitchute · 2025-10-01T21:24:51Z

Been waiting most of the day, but I think Decent CI is hung up here. Merging and moving on. Thanks all.

jmarrec

Just have a couple of questions / suggestions. Sorry for dropping in late.

I'm guessing you tested this with real world manufacturer data?

A datasets/ file would be nice, or at least one example file should use proper data.

jmarrec · 2025-10-03T07:27:08Z

testfiles/PlantLoopHeatPump_EIR_AirSource_and_AWHP.idf

+  Curve:Biquadratic,
+    CapCurveFuncTemp,        !- Name
+    0.5,                     !- Coefficient1 Constant
+    0.0,                     !- Coefficient2 x
+    0.0,                     !- Coefficient3 x**2
+    0.0,                     !- Coefficient4 y
+    0.0,                     !- Coefficient5 y**2
+    0.0,                     !- Coefficient6 x*y
+    5.0,                     !- Minimum Value of x
+    10.0,                    !- Maximum Value of x
+    24.0,                    !- Minimum Value of y
+    35.0,                    !- Maximum Value of y
+    ,                        !- Minimum Curve Output
+    ,                        !- Maximum Curve Output
+    Temperature,             !- Input Unit Type for X
+    Temperature,             !- Input Unit Type for Y
+    Dimensionless;           !- Output Unit Type
+
+  Curve:Biquadratic,
+    EIRCurveFuncTemp,        !- Name
+    1.0,                     !- Coefficient1 Constant
+    0.0,                     !- Coefficient2 x
+    0.0,                     !- Coefficient3 x**2
+    0.0,                     !- Coefficient4 y
+    0.0,                     !- Coefficient5 y**2
+    0.0,                     !- Coefficient6 x*y
+    5.0,                     !- Minimum Value of x
+    10.0,                    !- Maximum Value of x
+    24.0,                    !- Minimum Value of y
+    35.0,                    !- Maximum Value of y
+    ,                        !- Minimum Curve Output
+    ,                        !- Maximum Curve Output
+    Temperature,             !- Input Unit Type for X
+    Temperature,             !- Input Unit Type for Y
+    Dimensionless;           !- Output Unit Type
+
+  Curve:Quadratic,
+    EIRCurveFuncPLR,         !- Name
+    1.0,                     !- Coefficient1 Constant
+    0.0,                     !- Coefficient2 x
+    0.0,                     !- Coefficient3 x**2
+    0.0,                     !- Minimum Value of x
+    1.0;                     !- Maximum Value of x


Sorry for jumping late, i just noticed this PR dropping in develop yesterday and I am interested in the feature, as I have had to model AWHP before including some systems like the one mentioned in the PR's original post.

I'm a bit confused by these curves, and they seem really generic to mimic a real world system.

I'm sure the testfiles added are nice to ensure that a simulation runs and for coverage, but it's also an Example File, so does it mimic real world operation?

jmarrec · 2025-10-03T07:31:16Z

testfiles/PlantLoopHeatPump_EIR_AirSource_and_AWHP_cooling_only.idf

+  EnergyManagementSystem:Actuator,
+    opModeAct_cooling,       !- Name
+    test_AWHP,               !- Actuated Component Unique Name
+    HeatPump:AirToWater:Cooling,  !- Actuated Component Type
+    Operating Mode;          !- Actuated Component Control Type
+
+  EnergyManagementSystem:OutputVariable,
+    Operating Model Output Cooling,  !- Name
+    opModeAct_cooling,       !- EMS Variable Name
+    Averaged,                !- Type of Data in Variable
+    SystemTimeStep,          !- Update Frequency
+    ,                        !- EMS Program or Subroutine Name
+    ;                        !- Units
+
+  EnergyManagementSystem:ProgramCallingManager,
+    Change_OpMode_EMS_Program_Manager,  !- Name
+    InsideHVACSystemIterationLoop,  !- EnergyPlus Model Calling Point
+    Change_OpMode_EMS_Program;  !- Program Name 1
+
+  EnergyManagementSystem:Program,
+    Change_OpMode_EMS_Program,  !- Name
+    IF (Hour <= 12),         !- Program Line 2
+    SET opModeAct_cooling = 0,  !- <none>
+    ELSE,                    !- <none>
+    SET opModeAct_cooling = 1,  !- <none>
+    ENDIF;                   !- <none>


I don't get this EMS program here?

Again, this ends up being an Example File.

This is some example EMS code for controlling the operating mode. Do you feel it's too simplified and better be removed? I can update the example in a followup PR.

jmarrec · 2025-10-03T07:32:49Z

testfiles/PlantLoopHeatPump_EIR_AirSource_and_AWHP_cooling_only.idf

+! PlantLoopHeatPump_EIR_AirSource.idf
+!
+! Basic file description:
+! The EIR formulated air-to-water heat pump is demonstrated using a simple collection of plant loops.  Building loads
+! are represented using Plant Load Profile objects
+! Run:      1 design day.
+! Building: None.
+! System:   None.
+! Plant:    PLANT LOAD PROFILE with District Heating and Cooling as necessary.


The three testfiles added have exactly the same description. I feel like there should be be some difference here.

And the mention of the special shenanigans like the EMS program would probably be good for the heating/cooling only ones.

Indeed. I forgot to update the description. I will modify them.

Thanks for catching this and for all your review! @jmarrec

yujiex · 2025-10-03T18:30:11Z

Just have a couple of questions / suggestions. Sorry for dropping in late.

I'm guessing you tested this with real world manufacturer data?

A datasets/ file would be nice, or at least one example file should use proper data.

Yes, a Daikin engineer is using their performance data to test the model. But they don't want to reveal their product data, so the one here uses very generic setting in the curves. I'll try to create another example with more realistic data. I'll create a followup PR to add it in.

initial commit NFP doc

c0e677c

yujiex added NewFeature Includes code to add a new feature to EnergyPlus IDDChange Code changes impact the IDD file (cannot be merged after IO freeze) labels Mar 20, 2025

yujiex self-assigned this Mar 20, 2025

Add figures and correct equation format

5642f11

JasonGlazer reviewed Mar 24, 2025

View reviewed changes

Yujie Xu added 7 commits March 24, 2025 16:37

reformat idd comparison table

02c8433

edit md: reformat idd, add sizing factor

baded34

edit md: add output section

4c47dcf

edit md: notes on which model to choose

45a8fa0

edit md: add output table in html equipment summary

85a5ca7

edit md: separate output for heating cooling equip summary

c52ed87

edit md: separate water inlet outlet node for different plant loop

db3e3f9

Yujie Xu and others added 10 commits April 16, 2025 14:33

idd change initial commit

a2d3973

idd: remove condenser inlet/outlet nodes for now

d0769cc

fix idd missing "\field"

889124e

refine idd, add input reading code and test

5d90e1a

add test idf to CMakeLists

949dcae

add new AWHP to BranchNodeConnections

ca523ba

add doPhysics related changes, inlet outlet node input read

aa0a6f0

Merge remote-tracking branch 'origin/develop' into NewAWHPobject

0738a4e

fix merge issue

5960c16

fix unit test from merging

7c56192

Yujie Xu added 2 commits September 29, 2025 16:56

add speed ratio output

e547751

Merge remote-tracking branch 'origin/NewAWHPobject' into NewAWHPobject

d41d7dd

rraustad reviewed Sep 30, 2025

View reviewed changes

fix test idf output var ;

1b8bfa6

rraustad approved these changes Sep 30, 2025

View reviewed changes

update idf version numbers

0959bbf

dareumnam approved these changes Oct 1, 2025

View reviewed changes

fix output var spelling, format input files

7a0b1fa

mitchute merged commit d4b5202 into develop Oct 1, 2025
10 of 11 checks passed

mitchute deleted the NewAWHPobject branch October 1, 2025 21:25

jmarrec reviewed Oct 3, 2025

View reviewed changes

jmarrec mentioned this pull request Oct 3, 2025

E+ 25.2.0: Wrap HeatPump:AirToWater NREL/OpenStudio#5490

Closed

yujiex mentioned this pull request Oct 4, 2025

HeatPump:AirToWater followup PR update test idf #11251

Merged

20 tasks

joseph-robertson mentioned this pull request Oct 10, 2025

Fix #5490 - E+ 25.2.0: Wrap HeatPump:AirToWater NREL/OpenStudio#5496

Merged

19 tasks

Entries	Added to
HeatPumpAirToWaterCooling, HeatPumpAirToWaterHeating, HeatPumpAirToWater,	“ConnectionObjectType” in DataLoopNodes.hh “PlantEquipmentType” in Enums.hh
"HeatPump:AirToWater:Cooling", "HeatPump:AirToWater:Heating", "HeatPump:AirToWater",	PlantEquipTypeNames in DataPlant.hh “ConnectionObjectTypeNames” in BranchNodeConnections.cc
"HEATPUMP:AIRTOWATER:COOLING", "HEATPUMP:AIRTOWATER:HEATING", "HEATPUMP:AIRTOWATER",	“PlantEquipTypeNamesUC” in DataPlant.hh “ConnectionObjectTypeNamesUC” in BranchNodeConnections.cc


		Table 2. Input fields of the heat pump objects in EnergyPlus

		<table class="table table-bordered table-hover table-condensed">

		## Proposed Approach ##

		This new feature proposes to create a new input object, HeatPump:AirToWater.

		- time since defrost started, timeSinceStart

		Note that ambient air temperature is already an existing EnergyPlus actuator. It could be used in defrost calculation as well.

A new air to water heat pump object #11001

A new air to water heat pump object #11001

Uh oh!

Conversation

yujiex commented Mar 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Pull request overview

Description of the purpose of this PR

About the extended internal data structure arrays

Regression diffs

Pull Request Author

Reviewer

Uh oh!

EnergyArchmage commented Mar 21, 2025

Uh oh!

yujiex commented Mar 21, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

yujiex commented Apr 8, 2025

Uh oh!

yujiex commented Apr 14, 2025

Uh oh!

rraustad commented Sep 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

yujiex commented Sep 29, 2025

Uh oh!

github-actions bot commented Sep 30, 2025

⚠️ Regressions detected on macos-14 for commit 0f601d3

Uh oh!

github-actions bot commented Sep 30, 2025

⚠️ Regressions detected on ubuntu-24.04 for commit 0f601d3

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rraustad Sep 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Sep 30, 2025

⚠️ Regressions detected on macos-14 for commit 7af3821

Uh oh!

github-actions bot commented Sep 30, 2025

⚠️ Regressions detected on ubuntu-24.04 for commit 7af3821

Uh oh!

yujiex commented Mar 20, 2025 •

edited

Loading

rraustad commented Sep 29, 2025 •

edited

Loading

⚠️ Regressions detected on macos-14 for commit `0f601d3`

⚠️ Regressions detected on ubuntu-24.04 for commit `0f601d3`

rraustad Sep 30, 2025 •

edited

Loading

⚠️ Regressions detected on macos-14 for commit `7af3821`

⚠️ Regressions detected on ubuntu-24.04 for commit `7af3821`

⚠️ Regressions detected on macos-14 for commit `434addf`

⚠️ Regressions detected on ubuntu-24.04 for commit `434addf`

⚠️ Regressions detected on ubuntu-24.04 for commit `7ab7c32`

⚠️ Regressions detected on macos-14 for commit `7ab7c32`

jmarrec left a comment •

edited

Loading

jmarrec Oct 3, 2025 •

edited

Loading