You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have a small switch at the top of the page allowing the user to toggle between technical and layperson displays. Differences would include:
1- graph (produced in R) would have different units and labels. Units would be driving equivalents (miles driven per 100sq. feet cleared), which would be calculated by applying a simple conversion factor prior to final calculated values prior to plotting (for now, [value in CO2-eq]*1.86, but @teixeirak needs to verify).
2- The .csv for download would only show up on the technical display.
3- The users guide (.pdf) to which the "guide" link directs would differ.
I'd appreciate other suggestions from a layperson's perspective!
The text was updated successfully, but these errors were encountered:
If doing conversions please use a library. In R convertr is a good one that has no dependencies but if udunits is already a dependency it is worth using that library or perhaps https://rubygems.org/gems/numru-units/versions/1.9.0
Also includes a test for the climate regulating values SO
Closes#58 by hiding, then showing the dot message after processing
Supports #32 by adding a tabbed pane for the technical & layperson
output
It would be nice to have a small switch at the top of the page allowing the user to toggle between technical and layperson displays. Differences would include:
1- graph (produced in R) would have different units and labels. Units would be driving equivalents (miles driven per 100sq. feet cleared), which would be calculated by applying a simple conversion factor prior to final calculated values prior to plotting (for now, [value in CO2-eq]*1.86, but @teixeirak needs to verify).
2- The .csv for download would only show up on the technical display.
3- The users guide (.pdf) to which the "guide" link directs would differ.
I'd appreciate other suggestions from a layperson's perspective!
The text was updated successfully, but these errors were encountered: