Add output wetbulb globe temperature in the csv output #10506

yujiex · 2024-05-15T23:39:11Z

Pull request overview

Fixes Propose to add an "indoor Wet-bulb Globe Temperature" report variable #10504

introduction

This PR adds an Output:Variable, Wetbulb Globe Temperature, to the zone air report. Its calculation is as follows

Wetbulb Globe Temperature = 0.7 * zone wetbulb temperature + 0.3 * zone operative temperature

The attached file is a sample output file with the Wetbulb Globe Temperature added.

eplusout.csv

regression diffs

audit diffs are due to changes in the requested output variables

For example, in 1ZoneUncontrolled example file, NumOfRVariable increased by 2 as Wetbulb Globe Temperature and Wetbulb Temperature are added. The NumConsideredOutputVariables and NumOfRVariable(Actual) increases by 3 as 3 more Output:Variable are added to the idf.

rdd diffs are because 2 more variables are available with this feature. For example, this is the diffs for the 1ZoneUncontrolled.idf.

Table diffs are due to the added output variables. These table diffs are only present in 1ZoneUncontrolled and 5ZoneAirCooledWithSpacesHVAC as Output:Variable are added to these two files for testing.

Meter diffs happen in 1ZoneUncontrolled and 5ZoneAirCooledWithSpacesHVAC

in 1ZoneUncontrolled the "Meters for xx" index increased by 3 as 3 output:variables are requested for 1 zone; in 5ZoneAirCooledWithSpacesHVAC, the "Meters for xx" index increased by 14 as 2 outputs are requested for all 6 zones and two outputs are requested for one space
The following shows the added outputs in 5ZoneAirCooledWithSpacesHVAC.idf

  Output:Variable,Space 5 Office,Space Wetbulb Temperature,hourly; !- Zone Average [C]
  Output:Variable,Space 5 Office,Space Wetbulb Globe Temperature,hourly;
  Output:Variable,*,Zone Wetbulb Temperature,hourly; !- Zone Average [C]
  Output:Variable,*,Zone Wetbulb Globe Temperature,hourly;

NOTE: ENHANCEMENTS MUST FOLLOW A SUBMISSION PROCESS INCLUDING A FEATURE PROPOSAL AND DESIGN DOCUMENT PRIOR TO SUBMITTING CODE

Pull Request Author

Add to this list or remove from it as applicable. This is a simple templated set of guidelines.

Reviewer

This will not be exhaustively relevant to every PR.

mjwitte

@yujiex PsyTwbFnTdbWPb is an iterative calculation, so we try to avoid calculating it unless it's requested as an output variable or used as an EMS sensor. See NodeInputManager::CalcMoreNodeInfo for how this is managed for certain node outputs. It would be good to add a zone-level flag for this new output to skip the calculation if the variable has not been requested or used in EMS.

mjwitte · 2024-05-21T17:53:04Z

src/EnergyPlus/HeatBalanceAirManager.cc

@@ -4928,6 +4928,9 @@ void calcMeanAirTemps(EnergyPlusData &state,
    thisAirRpt.MeanAirTemp = ZTAV;
    thisAirRpt.MeanAirHumRat = airHumRatAvg;
    thisAirRpt.OperativeTemp = 0.5 * (ZTAV + MRT);
+    thisAirRpt.WetbulbTemp = Psychrometrics::PsyTwbFnTdbWPb(state, ZTAV, airHumRatAvg, state.dataEnvrn->OutBaroPress);
+    thisAirRpt.WetbulbGlobeTemp =
+        0.7 * Psychrometrics::PsyTwbFnTdbWPb(state, ZTAV, airHumRatAvg, state.dataEnvrn->OutBaroPress) + 0.3 * thisAirRpt.OperativeTemp;


Several lines below here, there is a block which recalculates thisAirRpt.OperativeTemp if operative temperature control is being used. Should the WetbulbGlobeTemp happen after that to be consistent?

Definitely, it should be after the thisAirRpt.OperativeTemp has been recalculated. Thanks for noticing this.

yujiex · 2024-05-21T18:18:30Z

@yujiex PsyTwbFnTdbWPb is an iterative calculation, so we try to avoid calculating it unless it's requested as an output variable or used as an EMS sensor. See NodeInputManager::CalcMoreNodeInfo for how this is managed for certain node outputs. It would be good to add a zone-level flag for this new output to skip the calculation if the variable has not been requested or used in EMS.

I will add a zone-level flag so that the calculation is only triggered if an output:variable is requested for this new wetbulb glob temperature variable.

The zone reporting flag will make sure the calculation only happens when the variable is requested The WBGT depends on the operative temperature (OT), so its calculation is moved to after OT obtains the most updated value.

only calculate WBGT when it is requested as a senser by EMS

mjwitte · 2024-05-22T21:13:56Z

src/EnergyPlus/HeatBalanceAirManager.cc

@@ -4902,6 +4903,22 @@ void ReportZoneMeanAirTemp(EnergyPlusData &state)
    // PURPOSE OF THIS SUBROUTINE:
    // This subroutine updates the report variables for the AirHeatBalance.

+    for (int ZoneLoop = 1; ZoneLoop <= state.dataGlobal->NumOfZones; ++ZoneLoop) {


This is good, but it needs to be protected by a oneTime variable so these loops don't execute every timestep.

Oh make sense. I will add the oneTime flag.

so that the reporting flag calculation only happens once

…atureOutput

mjwitte

@yujiex Sorry, I didn't think of this earlier, but this output variable will be generated for zones and for spaces (if state.dataHeatBal->doSpaceHeatBalanceSimulation is true), see ReportZoneMeanAirTemp).

mjwitte · 2024-05-23T19:49:14Z

src/EnergyPlus/HeatBalanceAirManager.cc

@@ -4902,6 +4903,25 @@ void ReportZoneMeanAirTemp(EnergyPlusData &state)
    // PURPOSE OF THIS SUBROUTINE:
    // This subroutine updates the report variables for the AirHeatBalance.

+    if (state.dataHeatBalAirMgr->CalcExtraReportVarMyOneTimeFlag) {


This is eerily similar to node wet-bulb temp. Shouldn't this be done over in NodeInputManager? and globe temp recorded as a node condition? Then these AirRpt variables could pick up data off the node.

for (auto const *reqVar : state.dataOutputProcessor->reqVars) { if (Util::SameString(reqVar->key, state.dataLoopNodes->NodeID(iNode)) || reqVar->key.empty()) { if (Util::SameString(reqVar->name, "System Node Wetbulb Temperature")) { state.dataNodeInputMgr->NodeWetBulbRepReq(iNode) = true; NodeWetBulbSchedPtr(iNode) = reqVar->SchedPtr; } else if (Util::SameString(reqVar->name, "System Node Relative Humidity")) { NodeRelHumidityRepReq(iNode) = true; NodeRelHumiditySchedPtr(iNode) = reqVar->SchedPtr; } else if (Util::SameString(reqVar->name, "System Node Dewpoint Temperature")) { NodeDewPointRepReq(iNode) = true; NodeDewPointSchedPtr(iNode) = reqVar->SchedPtr; } else if (Util::SameString(reqVar->name, "System Node Specific Heat")) { NodeSpecificHeatRepReq(iNode) = true; NodeSpecificHeatSchedPtr(iNode) = reqVar->SchedPtr; } } }

Is there one node in each space/zone? I didn't find out how to get the node index from space or zone index

if this mapping can be done relatively straightforward, then maybe I should calculate it at the nodes above and retrieve them during the reporting.

I'm not sure you want to make any big changes here. There is already Zone/Space Mean Air Temperature and these changes mimic that report variable. I am just pointing out that there may be a cleaner way to do this. If this PR is clean and gets the job done then that is good enough for now. A new branch could be used to test using the node condition as the basis for these AirRpt variables.

I see. I will test it out with some other test branches computing the node condition as the basis for the AirRpt variables.

One issue here is that node conditions are updated at the system timestep and these zone values are the averages at the zone timestep. So I'm not sure it's worth pursuing this.

Make sense. Maybe we can keep it as this and not calculate at the node level, otherwise, I assume there also needs to be some temporal aggregation steps in addition to node-to-zone/space matching.

Yes, keep it like this for now.

mjwitte · 2024-05-23T19:53:56Z

src/EnergyPlus/HeatBalanceAirManager.cc

+    if (state.dataHeatBalAirMgr->CalcExtraReportVarMyOneTimeFlag) {
+        for (int ZoneLoop = 1; ZoneLoop <= state.dataGlobal->NumOfZones; ++ZoneLoop) {
+            auto &thisZone = state.dataHeatBal->Zone(ZoneLoop);
+            for (auto const *reqVar : state.dataOutputProcessor->reqVars) {


For this use case, I think it's better to make reqVars the outer loop and check first for name="Zone Wetbulb Globe . . ." only first. Then if key.empty() set ReportWBGT for all zone (and spaces). If it's not empty, you can use FindItemInList to find the zone or space number and then set ReportWBGT for that single instance.

This way is better. I will loop through the reqVars first

mjwitte · 2024-05-23T19:55:32Z

src/EnergyPlus/HeatBalanceAirManager.cc

+            auto &thisZone = state.dataHeatBal->Zone(ZoneLoop);
+            for (auto const *reqVar : state.dataOutputProcessor->reqVars) {
+                if (Util::SameString(reqVar->key, thisZone.Name) || reqVar->key.empty()) {
+                    if (Util::SameString(reqVar->name, "Zone Wetbulb Globe Temperature")) {


if (reqVar->name == "ZONE WETBULB GLOBE TEMPERATURE")) {
name is already uppercase, so no need to use SameString here.

mjwitte · 2024-05-23T19:56:34Z

src/EnergyPlus/HeatBalanceAirManager.cc

+            }
+            for (int loop = 1; loop <= state.dataRuntimeLang->NumSensors; ++loop) {
+                if (state.dataRuntimeLang->Sensor(loop).UniqueKeyName == thisZone.Name &&
+                    Util::SameString(state.dataRuntimeLang->Sensor(loop).OutputVarName, "Zone Wetbulb Globe Temperature")) {


Here I'm not sure about the case of sensor OutputVarName so probably keep SameString.

mjwitte · 2024-05-23T20:02:25Z

src/EnergyPlus/HeatBalanceAirManager.cc

+    auto const &thisZone = state.dataHeatBal->Zone(zoneNum);
+    if (thisZone.ReportWBGT) {


If you move ReportWBGT into thisAirRpt (state.dataHeatBal->ZnAirRpt and spaceAirRpt) then it will work for both here.

good idea. I'll move it to be one of the fields in thisAirRpt

yujiex · 2024-05-23T21:05:23Z

doSpaceHeatBalanceSimulation

Thanks for noticing this. I will add another space layer in theReportWBGT flag calculation. I tested it with the "5ZoneAirCooledWithSpacesHVAC.idf" file. Looks like it's working

change loop order: *reqVar moved to the outer loop check first for variable name="Zone Wetbulb Globe . . ." Then if key.empty() set ReportWBGT for all zone (and spaces). If it's not empty, use FindItemInList to find the zone or space number and then set ReportWBGT for that single instance. reqVar->name changed to use "==" to check equality since it's upper case ReportWBGT moved into thisAirRpt, so it can work for both ZnAirRpt and spaceAirRpt

mjwitte · 2024-05-24T21:32:38Z

src/EnergyPlus/HeatBalanceAirManager.cc

+                        } else {
+                            auto &thisZnAirRpt = state.dataHeatBal->ZnAirRpt(ZoneLoop);
+                            thisZnAirRpt.ReportWBGT = true;


This should not be an else. If doSpaceHeatBalanceSimulation is true, then there will be values for both zones and spaces.

I see. I'll remove the else.

mjwitte · 2024-05-24T21:34:35Z

src/EnergyPlus/HeatBalanceAirManager.cc

+                    }
+                } else {
+                    if (state.dataHeatBal->doSpaceHeatBalanceSimulation) {
+                        int spaceNum = Util::FindItemInList(reqVar->name, state.dataHeatBal->space);


These need to search on reqVar->key, not name. If you run a test file with a zone name in the output variable object, it won't work here. And this needs to test for spaceNum > 0 to prevent a subscript error. Same comments apply to zone below.

I'll search the "key" field here for the space and zone name instead of the "name" field, and add a check for the space and zone index > 0.

mjwitte · 2024-05-24T21:35:17Z

src/EnergyPlus/HeatBalanceAirManager.cc

+                    } else {
+                        int ZoneLoop = Util::FindItemInList(reqVar->name, state.dataHeatBal->Zone);


Again, this shouldn't be an else.

Although here there should probably still be a separation based on state.dataHeatBal->doSpaceHeatBalanceSimulation T/F values, as when the spaceNum is found, the corresponding zone index containing this space will come from the zoneNum field of the space. When there's no space level simulations, a FindItemInList will be used to find the zone index

src/EnergyPlus/HeatBalanceAirManager.hh

mjwitte · 2024-05-28T17:32:31Z

src/EnergyPlus/DataHeatBalance.hh

@@ -1475,6 +1477,8 @@ namespace DataHeatBalance {
        Real64 OABalanceFanElec = 0.0;       // Fan Electricity {W} due to OA air balance
        Real64 SumEnthalpyM = 0.0;           // Zone sum of EnthalpyM
        Real64 SumEnthalpyH = 0.0;           // Zone sum of EnthalpyH
+        // reporting flags
+        bool ReportWBGT = true; // whether the wetbulb globe temperature is reqeusted as an output variable or used as an EMS sensor


Sorry - it's this flag that should be initialized to false.

Oh! right right. This should be false.

zone will report the variable when itself is requested and when its subspace is requested

when a specific space is requested to report WBGT, only that space is reported, not its parent zone. when no specific zone or space is requested, then Output:Variable,*,Zone Wetbulb Globe Temperature,hourly; -> report all zones Output:Variable,*,Space Wetbulb Globe Temperature,hourly;-> report all spaces

set up a Wetbulb Globe Temperature EMSInternalVariable for zone and space

mjwitte · 2024-05-30T18:29:49Z

src/EnergyPlus/HeatBalanceAirManager.cc

+                std::string const &spaceName = state.dataHeatBal->space(spaceNum).Name;
+                auto &thisSpaceAirRpt = state.dataHeatBal->spaceAirRpt(spaceNum);
+                SetupEMSInternalVariable(state, "Space Wetbulb Globe Temperature", spaceName, "[C]", thisSpaceAirRpt.WetbulbGlobeTemp);


This is not needed. Since the new WBGT is an output:variable is can be accessed with EMS:Sensor. The internal variable setup is to provide EMS access to values that are not time series data such as sizing results. See EMS Applicatoin Guide "Internal Variables" section.

If I don't add this, it doesn't show up in the edd file. Is that expected?

If I don't add this, it doesn't show up in the edd file. Is that expected?

Correct. The EDD will list available actuators and internal variables only. Everything in the RDD is available to use as an EMS sensor.

Thanks for the clarification. I will remove the SetupEMSInternalVariables.

mjwitte · 2024-05-30T18:30:10Z

src/EnergyPlus/HeatBalanceAirManager.cc

@@ -373,6 +377,8 @@ void GetSimpleAirModelInputs(EnergyPlusData &state, bool &ErrorsFound) // IF err
                            OutputProcessor::TimeStepType::System,
                            OutputProcessor::StoreType::Average,
                            name);
+
+        SetupEMSInternalVariable(state, "Zone Wetbulb Globe Temperature", name, "[C]", thisZnAirRpt.WetbulbGlobeTemp);


Same comment here, not needed.

mjwitte · 2024-05-30T18:44:32Z

src/EnergyPlus/HeatBalanceAirManager.cc

+            if (reqVar->name == "ZONE WETBULB GLOBE TEMPERATURE" || reqVar->name == "SPACE WETBULB GLOBE TEMPERATURE") {
+                if (reqVar->key.empty()) {
+                    for (int ZoneLoop = 1; ZoneLoop <= state.dataGlobal->NumOfZones; ++ZoneLoop) {
+                        if (state.dataHeatBal->doSpaceHeatBalanceSimulation) {
+                            for (int spaceNum : state.dataHeatBal->Zone(ZoneLoop).spaceIndexes) {
+                                auto &thisSpaceAirRpt = state.dataHeatBal->spaceAirRpt(spaceNum);
+                                thisSpaceAirRpt.ReportWBGT = true;
+                            }
+                        }
+                        auto &thisZnAirRpt = state.dataHeatBal->ZnAirRpt(ZoneLoop);
+                        thisZnAirRpt.ReportWBGT = true;
+                    }


Sorry I've made zone vs space so confusing. This code here will set ReportWBGT=true for all zones and spaces if either "Zone Wetbulb..." or "Space Webulb..." is requested. The structure should be more like:

if (reqVar->name == "ZONE WETBULB GLOBE TEMPERATURE"){ if (reqVar->key.empty()) { set true for all zones else set for matching zone name. } } if (state.dataHeatBal->doSpaceHeatBalanceSimulation) { if (reqVar->name == "SPACE WETBULB GLOBE TEMPERATURE"){ if (reqVar->key.empty()) { set true for all spaces else set for matching space name. } } }

I see I see. Cleaner this way. I had zones and space nested together earlier. I will change it to this format.

mjwitte · 2024-05-30T18:45:16Z

src/EnergyPlus/HeatBalanceAirManager.cc

+            if (state.dataRuntimeLang->Sensor(loop).OutputVarName == "ZONE WETBULB GLOBE TEMPERATURE" ||
+                state.dataRuntimeLang->Sensor(loop).OutputVarName == "SPACE WETBULB GLOBE TEMPERATURE") {


Similar comment here. If Zone then search for matching zone name, if Space, then search for matching space name.

I will change it to separate zone and space checks like the pattern you showed above

Just to make sure, I don't need to check state.dataRuntimeLang->Sensor(loop).UniqueKeyName.empty() right? They're guaranteed to be non-empty (otherwise it will err with "Unique Key Name not found.") @mjwitte

Just to make sure, I don't need to check state.dataRuntimeLang->Sensor(loop).UniqueKeyName.empty() right? They're guaranteed to be non-empty (otherwise it will err with "Unique Key Name not found.") @mjwitte

Correct.

Make the zone and space checks into the following pattern if (reqVar->name == "ZONE WETBULB GLOBE TEMPERATURE"){ if (reqVar->key.empty()) { set true for all zones else set for matching zone name. } } if (state.dataHeatBal->doSpaceHeatBalanceSimulation) { if (reqVar->name == "SPACE WETBULB GLOBE TEMPERATURE"){ if (reqVar->key.empty()) { set true for all spaces else set for matching space name. } } }

mjwitte

@yujiex This is getting close. See comments below, update with develop, and remove and temporary changes (e.g. Zone Wetbulb Temperature).

mjwitte · 2024-05-31T14:21:37Z

src/EnergyPlus/HeatBalanceAirManager.cc

+                }
+            }
+            if (state.dataHeatBal->doSpaceHeatBalanceSimulation) {
+                if (reqVar->key.empty()) {


Almost there. Before this line:
if (reqVar->name == "SPACE WETBULB GLOBE TEMPERATURE") {

Oh I forgot this space var check. Good catch

mjwitte · 2024-05-31T14:25:13Z

src/EnergyPlus/HeatBalanceAirManager.cc

+                    }
+                }
+            }
+            if (state.dataHeatBal->doSpaceHeatBalanceSimulation) {


This can be else if.

right. it should not check again if reqVar->name is already "ZONE WETBULB GLOBE TEMPERATURE"

mjwitte · 2024-05-31T14:25:48Z

src/EnergyPlus/HeatBalanceAirManager.cc

+                    thisZnAirRpt.ReportWBGT = true;
+                }
+            }
+            if (state.dataHeatBal->doSpaceHeatBalanceSimulation) {


I'll change to else if here

mjwitte · 2024-05-31T14:27:26Z

src/Transition/OutputRulesFiles/OutputChanges24-1-0-to-24-2-0.md

+
+### Adding an Output:Variable, Wetbulb Globe Temperature
+
+An output variable will be added, Wetbulb Globe Temperature.


This should list both flavors, Zone Wetbulb Globe Temperature and Space . . .

I'll add the space version too

…atureOutput

mjwitte

@yujiex This looks good, tested with various combinations of output variable and EMS sensor inputs. After you remove the Zone/Space Wetbulb Temperature from code and idfs, this will be ready to merge.

yujiex · 2024-06-04T16:34:03Z

@yujiex This looks good, tested with various combinations of output variable and EMS sensor inputs. After you remove the Zone/Space Wetbulb Temperature from code and idfs, this will be ready to merge.

Thanks @mjwitte. I just removed the wetbulb temperature output.

Myoldmopar · 2024-06-04T18:16:22Z

Wow. This has been run through the wringer! I'm not going to add more here, if it looks good at any point, merge away @mjwitte

Add output wetbulb globe temperature in csv output

17076f3

yujiex added the NewFeature Includes code to add a new feature to EnergyPlus label May 15, 2024

yujiex added this to the EnergyPlus 24.2 IOFreeze milestone May 15, 2024

yujiex self-assigned this May 15, 2024

Yujie Xu added 2 commits May 20, 2024 16:21

add documentation and output change notes

9d9396b

add another output of zone wetbulb temp for testing

0f777b3

yujiex requested review from Myoldmopar and JasonGlazer May 20, 2024 23:46

mjwitte reviewed May 21, 2024

View reviewed changes

Yujie Xu added 2 commits May 22, 2024 10:30

Move WBGT to after OT is updated, add zone reporting flag

ead87da

The zone reporting flag will make sure the calculation only happens when the variable is requested The WBGT depends on the operative temperature (OT), so its calculation is moved to after OT obtains the most updated value.

add the EMS senser check, clang-format

3843bee

only calculate WBGT when it is requested as a senser by EMS

Myoldmopar assigned mjwitte and unassigned yujiex May 22, 2024

mjwitte reviewed May 22, 2024

View reviewed changes

Yujie Xu added 2 commits May 22, 2024 14:42

add one time flag

27d4d95

so that the reporting flag calculation only happens once

Merge remote-tracking branch 'origin/develop' into wetBulbGlobeTemper…

be59dc3

…atureOutput

mjwitte reviewed May 23, 2024

View reviewed changes

Yujie Xu added 2 commits May 23, 2024 14:49

clang-format

2f320fc

mjwitte reviewed May 24, 2024

View reviewed changes

mjwitte reviewed May 28, 2024

View reviewed changes

Yujie Xu added 4 commits May 28, 2024 13:09

change ReportWBGT flag init value to false

cf6248c

remove else for zone ReportWBGT calc

6cfba45

zone will report the variable when itself is requested and when its subspace is requested

Add EMS sensor request code

8da2580

set up a Wetbulb Globe Temperature EMSInternalVariable for zone and space

mjwitte reviewed May 30, 2024

View reviewed changes

mjwitte reviewed May 31, 2024

View reviewed changes

Yujie Xu added 3 commits May 31, 2024 08:45

modify output change doc

b1ada59

add Space WBGT var checks, with else if

8af93d1

Merge remote-tracking branch 'origin/develop' into wetBulbGlobeTemper…

75f090c

…atureOutput

mjwitte approved these changes Jun 4, 2024

View reviewed changes

remove wetbulb temperature output (it's for debug purpose)

fb334d4

mjwitte merged commit 0f06ec3 into develop Jun 4, 2024
15 checks passed

mjwitte deleted the wetBulbGlobeTemperatureOutput branch June 4, 2024 19:54

		auto const &thisZone = state.dataHeatBal->Zone(zoneNum);
		if (thisZone.ReportWBGT) {

		} else {
		int ZoneLoop = Util::FindItemInList(reqVar->name, state.dataHeatBal->Zone);

		if (state.dataRuntimeLang->Sensor(loop).OutputVarName == "ZONE WETBULB GLOBE TEMPERATURE" \|\|
		state.dataRuntimeLang->Sensor(loop).OutputVarName == "SPACE WETBULB GLOBE TEMPERATURE") {


		### Adding an Output:Variable, Wetbulb Globe Temperature

		An output variable will be added, Wetbulb Globe Temperature.

Add output wetbulb globe temperature in the csv output #10506

Add output wetbulb globe temperature in the csv output #10506

Conversation

yujiex commented May 15, 2024 • edited

Pull request overview

introduction

regression diffs

Pull Request Author

Reviewer

mjwitte left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yujiex commented May 21, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mjwitte left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yujiex commented May 23, 2024 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mjwitte left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mjwitte left a comment • edited

Choose a reason for hiding this comment

yujiex commented Jun 4, 2024

Myoldmopar commented Jun 4, 2024

yujiex commented May 15, 2024 •

edited

yujiex commented May 23, 2024 •

edited

mjwitte left a comment •

edited