Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various UI changes required for Beta 1 (MVP) release #322

Open
4 of 14 tasks
stevebreit opened this issue Mar 19, 2025 · 0 comments
Open
4 of 14 tasks

Various UI changes required for Beta 1 (MVP) release #322

stevebreit opened this issue Mar 19, 2025 · 0 comments
Labels
good first issue Good for newcomers heat-app-js Issues related to the HEAT app frontend

Comments

@stevebreit
Copy link
Collaborator

stevebreit commented Mar 19, 2025

Changes requested below are based on testing https://heat-stack.fly.dev/single

Essential changes:

  • Change tab name from Epic Notes to HEAT analysis tool
  • Remove sample inputs in all fields above Energy Use History except as follows:
    • In the Design Temperature Override field, change text from “(Optional)” to “Optional”, i.e. omit parentheses
    • In the Setback Temperature field, make the default value “Optional”
    • In the Setback hours per day field, make the default value “Optional”
  • For the *Resident/*Client field, change the label to Resident/Client Name(s). Remove the Name label that appears below that in a smaller-size font.
  • For the Address field, the label Address appears twice, first in a larger-size font and again in a smaller-size font. Change the first occurrence from Address to Street Address, City, State. Remove the second Address label that appears below in smaller-size font.
  • For the Living Area field, greatly reduce vertical space between the field and the tip below that says The home’s above-grade conditioned space.
  • Add vertical space between the large Existing Heating System label and the smaller Fuel Type label. Make it similar or the same as spacing below the Home Information label at the top of the form.
  • In the label below the Design Temperature Override field, the value 65 should be dynamic, based on the lookup from the county-specific data embedded in our code (or read from a CSV file?). The typical value in MA is 5-to-15 degrees F.
  • In the label below the Setback hours per day field, remove the line that says Typical natural gas efficiency is 80%-95%.
  • Is there any difference in function between the Upload button and the Recalculate button? If not, I suggest the following:
    • Remove the Recalculate button (it’s in an odd place considering it’s only needed if someone changes the fields above the Energy Use History. When you remove it, leave the same amount of vertical space that it currently occupies.
    • Move the Upload button to its own line (below the filename field) and change it’s label to Calculate
  • For the value displayed under Average Indoor Temperature, display only one digit after the decimal point.

Non-Essential changes (Nice to Have)

  • In the table of delivery periods, the periods should be sorted in ascending order by Start Date regardless of the listing order in the input CSV file. The Feldman case can be used for testing this.
  • On the Whole-Home Heat Loss Comparison, display the equation for the Trend Line and the Rsquared value for the fit.
  • On the Whole-Home Heat Loss Comparison graph, display the trend line in the same color and thickness as the legend.
  • In the label below the Setback Temperature field, change working to work (for grammatical consistency with sleep)
@stevebreit stevebreit changed the title Various UI changes for Beta 1 Various UI changes required for Beta 1 (MVP) release Mar 19, 2025
@thadk thadk added good first issue Good for newcomers heat-app-js Issues related to the HEAT app frontend labels Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers heat-app-js Issues related to the HEAT app frontend
Projects
None yet
Development

No branches or pull requests

2 participants