Add new people schedule columns to EIO/initialization summary to address #10314 #10437

JasonGlazer · 2024-03-14T12:44:01Z

Pull request overview

Fixes "Nominal Min/Max Number of People" in People Internal Gains Nominal table includes effect of design day schedules #10314

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.

…port columns to use it.

JasonGlazer · 2024-03-14T20:29:58Z

This is impacting every EIO file that has lighting or internal equipment, in other words, all of them. But It is simply renaming two columns and adding six new columns to the internal load reports so that is expected. I spot checked a bunch of files and they are doing as expected and nothing more.

The 2.7% decrease in speed does not make sense to me. @Myoldmopar is that possibly due to something else going on? This only impacts the routine that populates the EIO file from internal games.

Based on this, I think this is ready to review. Since this is changing output it is on track for 24.2 so it is not critical this week.

JasonGlazer · 2024-03-18T12:57:02Z

The documentation updates should be done soon.

rraustad · 2024-03-19T13:09:59Z

src/EnergyPlus/ScheduleManager.cc

+                break;
+            case DayTypeGroup::WeekEndHoliday:
+                dayTypeFilter = {true, false, false, false, false, false, true, true, false, false, false, false};
+                break;


Is there something else needed here to include holidays?

The first true is Sunday, then five falses are Monday to Friday, then true for Saturday and then true for Holiday.

I see, my comment shows Sunday twice. I should probably verify which one is really Sunday :-)

The other thing I noticed is that this dayTypeFilter array is a constexpr for each day type. It would be nice to set these up at compile time and somehow use the correct array in the loop below.

I fixed the comment based on the enumeration:

EnergyPlus/src/EnergyPlus/ScheduleManager.hh

Lines 73 to 90 in 8955374

enum class DayType

{

Invalid = -1,

Dummy = 0,

Sunday = 1,

Monday,

Tuesday,

Wednesday,

Thursday,

Friday,

Saturday,

Holiday,

SummerDesignDay,

WinterDesignDay,

CustomDay1,

CustomDay2,

Num

};

And changed to using std::array so I can make these constexpr.

rraustad · 2024-03-19T13:25:06Z

This does look like a change only to output reporting yet there are other diffs. For example,

FCfactor data is not reported, which looks correct for 5ZoneAirCooledWithSpaceHeatBalance and 5ZoneAirCooledWithSpaces, but what change caused that diff?

 ! ,Jan{C},Feb{C},Mar{C},Apr{C},May{C},Jun{C},Jul{C},Aug{C},Sep{C},Oct{C},Nov{C},Dec{C}
  Site:GroundTemperature:BuildingSurface,  20.03,  20.03,  20.13,  20.30,  20.43,  20.52,  20.62,  20.77,  20.78,  20.55,  20.44,  20.20
-! ,Jan{C},Feb{C},Mar{C},Apr{C},May{C},Jun{C},Jul{C},Aug{C},Sep{C},Oct{C},Nov{C},Dec{C}
- Site:GroundTemperature:FCfactorMethod,  -1.89,  -3.06,  -0.99,   2.23,  10.68,  17.20,  21.60,  22.94,  20.66,  15.60,   8.83,   2.56
 ! ,Jan{C},Feb{C},Mar{C},Apr{C},May{C},Jun{C},Jul{C},Aug{C},Sep{C},Oct{C},Nov{C},Dec{C}
  Site:GroundTemperature:Shallow,  13.00,  13.00,  13.00,  13.00,  13.00,  13.00,  13.00,  13.00,  13.00,  13.00,  13.00,  13.00

and the actual input file location object info is reported now, not the weather file used (../testfiles/CMakeLists.txt). Maybe because this branch is behind develop? I would think if we report the input file location, then we should also report the weather file used?

-Site:Location,Chicago Ohare Intl Ap IL USA TMY3 WMO#=725300,41.98,-87.92,-6.00,201.00,98934,1.1759
+Site:Location,CHICAGO_IL_USA TMY2-94846,41.78,-87.75,-6.00,190.00,99063,1.1774

and a small diff radiant to convective decay curve data (0.30 vs 0.31) which may be the reason for the zone and component sizing diffs.

-Radiant to Convective Decay Curves for Cooling,SPACE2-1,C2-1, 0.275, 0.073, 0.062, 0.051, 0.044, 0.039, 0.036, 0.033, 0.030, 0.028, 0.026, 0.025, 0.022, 0.022, 0.019, 0.018, 0.017, 0.016, 0.015, 0.014, 0.013, 0.013, 0.012, 0.011, 0.011, 0.010, 0.009, 0.009, 0.008, 0.008, 0.007, 0.007, 0.007, 0.006, 0.006, 0.006
+Radiant to Convective Decay Curves for Cooling,SPACE2-1,C2-1, 0.275, 0.073, 0.062, 0.051, 0.044, 0.039, 0.036, 0.033, 0.031, 0.028, 0.026, 0.025, 0.022, 0.022, 0.019, 0.018, 0.017, 0.016, 0.015, 0.014, 0.013, 0.013, 0.012, 0.011, 0.011, 0.010, 0.009, 0.009, 0.008, 0.008, 0.007, 0.007, 0.007, 0.006, 0.006, 0.006

JasonGlazer · 2024-03-19T13:49:25Z

@rraustad I'm going to remerge and try it again since I only added documentation changes last time and time before that I was only showing the EIO diffs.

rraustad · 2024-03-19T14:44:05Z

src/EnergyPlus/ScheduleManager.cc

+                    if (dayTypeFilter[jType - 1]) {
+                        auto &daySch = state.dataScheduleMgr->DaySchedule;
+                        MinValue = min(MinValue, minval(daySch(weekSch.DaySchedulePointer(jType)).TSValue));
+                        MaxValue = max(MaxValue, maxval(daySch(weekSch.DaySchedulePointer(jType)).TSValue));


And here:

auto &daySch = state.dataScheduleMgr->DaySchedule(weekSch.DaySchedulePointer(jType));

Got it, thanks

rraustad · 2024-03-19T15:10:20Z

Noticing an issue when the day type (e.g., SummerDesignDay vs WinterDesignDay) is called out in different "For" groups. Using 5ZoneAirCooledWithSpaceHeatBalance.idf.

Schedule:Compact,
  EQUIP-1,                 !- Name
  Fraction,                !- Schedule Type Limits Name
  Through: 12/31,          !- Field 1
  For: WeekDays SummerDesignDay CustomDay1 CustomDay2, !- Field 2
  Until: 8:00,0.02,        !- Field 3
  Until: 9:00,0.4,         !- Field 5
  Until: 14:00,0.9,        !- Field 7
  Until: 15:00,0.8,        !- Field 9
  Until: 16:00,0.7,        !- Field 11
  Until: 18:00,0.5,        !- Field 13
  Until: 20:00,0.3,        !- Field 15
  Until: 24:00,0.02,       !- Field 17
  For: Weekends WinterDesignDay Holiday, !- Field 19
  Until: 24:00,0.2;        !- Field 20

The data is correct (i.e., the minimum for all design days is a 0.02 multiplier), however, I am wondering if internal gains on a summer design day vs winter design day are important enough for a dedicated column? Here the minimum for a winter design day should match Weekends/Holidays column using a 0.2 multiplier.

Develop results as a comparison for reviewer:

rraustad · 2024-03-19T15:12:32Z

And wondering if CustomDay1 and 2 need their own columns?

rraustad · 2024-03-19T15:13:40Z

I pulled develop and the unit tests run successfully.

JasonGlazer · 2024-03-19T21:50:24Z

And wondering if CustomDay1 and 2 need their own columns?

I considered it but decided that they were not used much (at least as far as I could tell).

JasonGlazer · 2024-04-09T12:51:31Z

internal gains on a summer design day vs winter design day are important enough for a dedicated column

Interesting idea so you are suggesting separate min and max for summer design day and for winter design day. Another two columns. I can do that if you think it would be useful. I would guess for many modelers the design day values for these are constant so the min for the winter and the max for the summer will probably show the values they care about. But if you think it will be useful, I can add them.

rraustad · 2024-04-09T12:54:33Z

@JasonGlazer I'm not sure if it is useful or not. @mjwitte ?

rraustad · 2024-04-09T15:08:36Z

src/EnergyPlus/ScheduleManager.cc

+            ShowFatalError(state, "getScheduleMinMaxByDayType called with ScheduleIndex out of range");
+        } else if (ScheduleIndex > 0) {
+            std::array<bool, maxDayTypes> dayTypeFilter;
+            std::fill(dayTypeFilter.begin(), dayTypeFilter.end(), false);


Is this initialization (4517) really necessary if you are going to fill this array anyway with one of the below? Also, ScheduleIndex < 1 (line 4513) is after testing for ScheduleIndex == -1 (4507) and == 0 (4510). Is it even possible for a schedule index to be less than -1? if not, then ScheduleIndex < 1 at line 4515 is not needed (not sure that fatal is needed either but it's safe). Ideally, if the fatal were not there then if (ScheduleIndex > 0) could be first in the IF ladder since it is most common. This is probably way too picky for something that has limited use for the new table columns.

@rraustad thanks for the careful review. I think I addressed your suggestions with the latest comit.

…hope)

JasonGlazer · 2024-04-12T22:00:04Z

I looked through all the warnings and the EIOs changed as expected. I spot checked a bunch. This is ready for review.

rraustad

This looks good now.

rraustad · 2024-04-15T13:01:14Z

src/EnergyPlus/InternalHeatGains.cc

+                      "Convected,Sensible Fraction Calculation,Activity level,ASHRAE 55 Warnings,Carbon Dioxide Generation Rate,"
+                      "Minimum Number of People for All Day Types,Maximum Number of People for All Day Types,"
+                      "Minimum Number of People for Weekdays, Maximum Number of People for Weekdays, "
+                      "Minimum Number of People for Weekends/Holidays, Maximum Number of People for Weekends /Holidays,"


The extra space in the maximum column (Weekends /Holidays) actually has a good result on the column heading.

rraustad · 2024-04-15T13:09:27Z

src/EnergyPlus/ScheduleManager.cc

+            false, false, false, false, false, false, false, false, false, true, false, false};
+        constexpr std::array<bool, maxDayTypes> dayTypeFilterNone = {
+            false, false, false, false, false, false, false, false, false, false, false, false};
+        if (ScheduleIndex > 0 && ScheduleIndex <= state.dataScheduleMgr->NumSchedules) {


I am trying to convince myself that it is even possible for ScheduleIndex > NumSchedules. Not all functions in ScheduleManager use this check (i.e., ScheduleIndex <= NumSchedules). The only way to get an index is to call GetScheduleIndex, which uses FindItemInList and will either return a valid index or 0. I'm not convinced yet so nothing to do here. While investigating this I noticed in GetScheduleIndex that WeekSchedule(Schedule().WeekSchedulePointer()).Used and WeekSchedule(Schedule().WeekSchedulePointer()).DaySchedulePointer().Used are set but never used anywhere.

Used variables are never used. Alanis would be proud of that irony.

rraustad · 2024-04-15T13:20:10Z

src/EnergyPlus/ScheduleManager.cc

+                // store for the next call of the same schedule
+                curSch.MaxByDayType[curDayTypeGroup] = MaxValue;
+                curSch.MinByDayType[curDayTypeGroup] = MinValue;
+                curSch.MaxMinByDayTypeSet[curDayTypeGroup] = true;


There is another loop over people schedules in DetermineSystemPopulationDiversity. Not sure if this could help there or if when checking those people schedules these 3 values could be set to save even more simulation time.

rraustad · 2024-04-15T13:33:55Z

The new design day columns also highlight what is happening on the design days. That was a good addition.

rraustad · 2024-04-15T13:42:28Z

doc/output-details-and-examples/src/output-files/eplusout-eio.tex


-People Internal Gains,~ SPACE1-1 PEOPLE 1, OCCUPY-1, SPACE1-1, 99.16, 11.0, 11.0, 0.111, 9.015, 0.300, 0.700, AutoCalculate, ACTSCHD, No, 3.8200E-008, 0, 11
+ People Internal Gains Nominal,  SPACE1-1 PEOPLE 1, OCCUPY-1, SPACE1-1, 90.00, 10.0, 10.0, 0.111, 9.009, 0.300, 0.700, 0.550, ACTSCHD, No, 3.8200E-008, 0.0, 10.0, 0.8, 4.0, 0.6, 2.5, 9.5, 10.0, 0.0, 0.5, 


Noticed here that for all the internal gain tables the word Nominal was added to the table title. That is important enough to note in OutputChanges.

Correction. The word "Nominal" is added to the eio title and was already included in the html using develop. So nothing to do here.

rraustad · 2024-04-15T13:47:17Z

doc/output-details-and-examples/src/output-files/eplusout-eio.tex

-This numeric field is the calculated maximum amount of lighting in Watts based on the calculated lighting level (above) * the maximum value (annual) for the lights schedule. It may be useful in diagnosing errors that occur during simulation.
+\subsubsection{Field: Minimum Lighting Level for Weekdays \{W\}}\label{field-minimum-lighting-level-for-weekdays-w}
+
+This numeric field is the calculated minimum amount of lighting in Watts based on the calculated lighting level (above) * the minimum value for the lights schedule for weekday day types (Monday through Friday).


Noting that the wording from here forward is different from the description of people.

based on the number of people field based on the calculated lighting level (above)

rraustad · 2024-04-15T13:58:00Z

tst/EnergyPlus/unit/ScheduleManager.unit.cc

+
+    std::tie(schMin, schMax) = getScheduleMinMaxByDayType(*state, index, DayTypeGroup::WinterDesignDay);
+    EXPECT_EQ(0.16, schMin);
+    EXPECT_EQ(0.25, schMax);


It took me a minute to see the 2 WinterDesignDay in the HIGHLOW02 schedule. Same for other schedule types. Good unit test.

rraustad · 2024-04-15T13:59:31Z

Pulled develop and unit tests run to completion.

rraustad · 2024-04-15T14:31:22Z

I think because there was [decent_ci_skip] in the last commit there are no results to review.

mjwitte · 2024-04-15T15:42:13Z

I think because there was [decent_ci_skip] in the last commit there are no results to review.

There are results under the previous commit.

b912be3#comments

JasonGlazer · 2024-04-15T17:14:52Z

I think because there was [decent_ci_skip] in the last commit there are no results to review.

There are results under the previous commit.

Sorry, I didn't realize that adding [decent_ci_skip] would make accessing those previous CI results more difficult.

rraustad · 2024-04-15T22:50:43Z

Yes, the only diffs are shown in the eio file for internal gains information. For 1ZoneDataCenterCRAC_wApproachTemp the schedule is always 1 so the new data for min/max internal gains for all day types is the same as the peak value of 50000 W.

Schedule:Constant,Data Center Operation Schedule,Any Number,1.0;

-! ,Name,Schedule Name,Zone Name,Zone Floor Area {m2},# Zone Occupants,Equipment Level {W},Equipment/Floor Area {W/m2},Equipment per person {W/person},Fraction Convected,CPU End-Use SubCategory,Fan End-Use SubCategory,UPS End-Use SubCategory,Nominal Minimum Equipment Level {W},Nominal Maximum Equipment Level {W}, Design Air Volume Flow Rate {m3/s}
- ElectricEquipment:ITE:AirCooled Internal Gains Nominal, DATA CENTER SERVERS,DATA CENTER OPERATION SCHEDULE,MAIN ZONE,232.26,0.0,50000.000,215.278,1.0,ITE-CPU,ITE-Fans,ITE-UPS,5000.000,50000.000,5.0000000000
+! ,Name,Schedule Name,Zone Name,Zone Floor Area {m2},# Zone Occupants,Equipment Level {W},Equipment/Floor Area {W/m2},Equipment per person {W/person},Fraction Convected,CPU End-Use SubCategory,Fan End-Use SubCategory,UPS End-Use SubCategory,Minimum Equipment Level for All Day Types {W},Maximum Equipment Level for All Day Types {W},Minimum Equipment Level for Weekdays {W}, Maximum Equipment Level for Weekdays {W},Minimum Equipment Level for Weekends/Holidays {W}, Maximum Equipment Level for Weekends /Holidays {W},Minimum Equipment Level for Summer Design Days {W}, Maximum Equipment Level for Summer Design Days {W},Minimum Equipment Level for Winter Design Days {W}, Maximum Equipment Level for Winter Design Days {W},Design Air Volume Flow Rate {m3/s}
+ ElectricEquipment:ITE:AirCooled Internal Gains Nominal, DATA CENTER SERVERS,DATA CENTER OPERATION SCHEDULE,MAIN ZONE,232.26,0.0,50000.000,215.278,N/A,1.0,ITE-CPU,ITE-Fans,ITE-UPS,5000.000,50000.000,50000.000,50000.000,50000.000,50000.000,50000.000,50000.000,50000.000,50000.000,5.0000000000

rraustad · 2024-04-15T22:53:00Z

@JasonGlazer are there any other changes planned? @Myoldmopar this is ready to go if no other changes planned.

JasonGlazer · 2024-04-16T10:58:49Z

@JasonGlazer are there any other changes planned? @Myoldmopar this is ready to go if no other changes planned.

@rraustad thanks for the careful review. I have no other changes planned so this is ready to go.

mjwitte · 2024-04-24T17:19:12Z

src/EnergyPlus/ScheduleManager.cc

+                    for (int jType = 1; jType <= maxDayTypes; ++jType) {
+                        if (dayTypeFilter[jType - 1]) {
+                            auto &daySch = state.dataScheduleMgr->DaySchedule(weekSch.DaySchedulePointer(jType));
+                            MinValue = min(MinValue, minval(daySch.TSValue));
+                            MaxValue = max(MaxValue, maxval(daySch.TSValue));
+                        }


Rather than cycle through the entire schedule for every daytype group, why not cycle through once and store the max/min for each day type first? Then cycle through those to sort into the DayTypeGroups.

@mjwitte I did some optimization of this loop that should greatly improve it's performance although it is not exactly using the approach you suggested.

JasonGlazer · 2024-04-26T13:15:40Z

This is running slightly faster than develop now!

JasonGlazer · 2024-04-26T13:35:04Z

All the warnings are EIO diffs. I spot checked them again and saw nothing that we weren't expecting. I think this is ready for a final review and (hopefully) merge.

Myoldmopar

No problem here.

Myoldmopar · 2024-05-02T13:33:09Z

src/EnergyPlus/ScheduleManager.cc

+            false, false, false, false, false, false, false, false, false, true, false, false};
+        constexpr std::array<bool, maxDayTypes> dayTypeFilterNone = {
+            false, false, false, false, false, false, false, false, false, false, false, false};
+        if (ScheduleIndex > 0 && ScheduleIndex <= state.dataScheduleMgr->NumSchedules) {


Used variables are never used. Alanis would be proud of that irony.

Myoldmopar · 2024-05-02T13:34:01Z

src/EnergyPlus/ScheduleManager.hh

@@ -69,6 +69,7 @@ struct EnergyPlusData;
 namespace ScheduleManager {

    constexpr int ScheduleAlwaysOn = -1;
+    constexpr int ScheduleAlwaysOff = 0;


Much better than a magic number used everywhere, nice.

Myoldmopar · 2024-05-03T14:29:35Z

src/EnergyPlus/ScheduleManager.hh

+        std::array<bool, static_cast<int>(DayType::Num)> MaxMinByDayTypeSet{
+            false}; // minimum and maximum values by daytype have been stored for this schedule
+        std::array<Real64, static_cast<int>(DayType::Num)> MinByDayType{0.0}; // minimum values by daytype for this schedule
+        std::array<Real64, static_cast<int>(DayType::Num)> MaxByDayType{0.0}; // maximum values by daytype for this schedule


Multiple arrays allocated to the same size hints that they may be nicer as a single struct. Not a big deal since there are just 3 arrays, but if it grew to more, it might be worthwhile.

Myoldmopar · 2024-05-03T14:42:08Z

EIO diffs as expected, but builds and tests happily locally. I think this is ready to go, I'm going to merge. Thanks @JasonGlazer !

JasonGlazer added 2 commits March 13, 2024 16:54

Add new function for min max by daytype and new EIO/initialization re…

a673de6

…port columns to use it.

Add unit test

60fe6f9

JasonGlazer added the Defect Includes code to repair a defect in EnergyPlus label Mar 14, 2024

JasonGlazer added this to the EnergyPlus 24.2 milestone Mar 14, 2024

JasonGlazer self-assigned this Mar 14, 2024

Add support for other internal load equipment.

26f96b0

JasonGlazer marked this pull request as ready for review March 14, 2024 20:25

JasonGlazer requested review from Myoldmopar and mjwitte March 14, 2024 20:31

JasonGlazer mentioned this pull request Mar 14, 2024

"Nominal Min/Max Number of People" in People Internal Gains Nominal table includes effect of design day schedules #10314

Closed

3 tasks

JasonGlazer added the OutputChange Code changes output in such a way that it cannot be merged after IO freeze label Mar 18, 2024

JasonGlazer added 2 commits March 18, 2024 08:03

Update output-details-and-examples for People

ed9c634

Add new EIO outputs for remaining changes to output-details-and-examples

8955374

rraustad reviewed Mar 19, 2024

View reviewed changes

JasonGlazer added 2 commits April 9, 2024 07:07

Merge branch 'develop' into Fix10314-AddingScheduleColumns

f4280d1

Using constexpr for dayfilters

5957438

JasonGlazer added 2 commits April 9, 2024 09:24

clean ups

f32e3c7

clang format (although not actually better)

5f0010a

rraustad reviewed Apr 9, 2024

View reviewed changes

JasonGlazer added 4 commits April 12, 2024 08:04

Retype code changes [decent_ci_skip]

7f6925c

Move initialization out of constructor to make clang format happy (I …

9c6a8e7

…hope)

Merge branch 'develop' into Fix10314-AddingScheduleColumns

b912be3

Add OutputChanges24-1-0-to-24-2-0.md [decent_ci_skip] [actions skip]

50b7a43

JasonGlazer requested a review from rraustad April 15, 2024 11:33

rraustad approved these changes Apr 15, 2024

View reviewed changes

rraustad reviewed Apr 15, 2024

View reviewed changes

Myoldmopar added the HighComplexityApproved Used for subcontractor defect complexity requests label Apr 24, 2024

mjwitte reviewed Apr 24, 2024

View reviewed changes

JasonGlazer added 3 commits April 25, 2024 09:23

Merge branch 'develop' into Fix10314-AddingScheduleColumns

77ed130

Utilize SetScheduleMinMax and optimize loop

b8d9928

Don't iterate through duplicate week schedules when finding min and max.

8475b71

Myoldmopar self-assigned this Apr 30, 2024

Myoldmopar approved these changes May 3, 2024

View reviewed changes

Myoldmopar merged commit 54ea3ea into develop May 3, 2024
15 checks passed

Myoldmopar deleted the Fix10314-AddingScheduleColumns branch May 3, 2024 14:42

	enum class DayType
	{
	Invalid = -1,
	Dummy = 0,
	Sunday = 1,
	Monday,
	Tuesday,
	Wednesday,
	Thursday,
	Friday,
	Saturday,
	Holiday,
	SummerDesignDay,
	WinterDesignDay,
	CustomDay1,
	CustomDay2,
	Num
	};


		People Internal Gains,~ SPACE1-1 PEOPLE 1, OCCUPY-1, SPACE1-1, 99.16, 11.0, 11.0, 0.111, 9.015, 0.300, 0.700, AutoCalculate, ACTSCHD, No, 3.8200E-008, 0, 11
		People Internal Gains Nominal, SPACE1-1 PEOPLE 1, OCCUPY-1, SPACE1-1, 90.00, 10.0, 10.0, 0.111, 9.009, 0.300, 0.700, 0.550, ACTSCHD, No, 3.8200E-008, 0.0, 10.0, 0.8, 4.0, 0.6, 2.5, 9.5, 10.0, 0.0, 0.5,

Add new people schedule columns to EIO/initialization summary to address #10314 #10437

Add new people schedule columns to EIO/initialization summary to address #10314 #10437

Conversation

JasonGlazer commented Mar 14, 2024 • edited by rraustad Loading

Pull request overview

Pull Request Author

Reviewer

JasonGlazer commented Mar 14, 2024

JasonGlazer commented Mar 18, 2024

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

rraustad commented Mar 19, 2024 • edited Loading

JasonGlazer commented Mar 19, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rraustad commented Mar 19, 2024

rraustad commented Mar 19, 2024

rraustad commented Mar 19, 2024

JasonGlazer commented Mar 19, 2024

JasonGlazer commented Apr 9, 2024 • edited Loading

rraustad commented Apr 9, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

JasonGlazer commented Apr 12, 2024

rraustad left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rraustad Apr 15, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rraustad commented Apr 15, 2024

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

rraustad commented Apr 15, 2024

rraustad commented Apr 15, 2024

mjwitte commented Apr 15, 2024

JasonGlazer commented Apr 15, 2024 • edited Loading

rraustad commented Apr 15, 2024

rraustad commented Apr 15, 2024

JasonGlazer commented Apr 16, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

JasonGlazer commented Apr 26, 2024

JasonGlazer commented Apr 26, 2024

Myoldmopar 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

Myoldmopar commented May 3, 2024

JasonGlazer commented Mar 14, 2024 •

edited by rraustad

Loading

rraustad commented Mar 19, 2024 •

edited

Loading

JasonGlazer commented Apr 9, 2024 •

edited

Loading

rraustad Apr 15, 2024 •

edited

Loading

JasonGlazer commented Apr 15, 2024 •

edited

Loading