caware / c-vis Goto Github PK

Nodes should be sorted by alphabetical for function, and floor for geographical

With view for creating tabbed style visualisations - monthly data, daily data, sunburst, radar / streamgraph

Increase maximum amount of plots to 10.

Use Chrome Frame when an IE user visits

Add in additional main power meter into tree.

Multiple sensors of the same type should be dealt with - Raw sensor names in each room when multiple rooms are used.

Becomes very very sluggish around 3 months worth.

Bash / python script to check presence of console.log() etc strings for production version.

Add ability to graph data that represents all functions IE: all Sockets, all Sockets on the first floor etc.

Plot code to decide how many lines to draw is stupid and hacky.

Midnight lines on the charts are too hard to see on some screens.

Two sensors, one in FW10, one in SW05 both labelled as 'Power', S-m31 and S-m29 respectively - what are these!?

Add links to raw sensor data used for charting, as well as the sensor index files.

Find out the status of the 257 overall meter, change the labels to have similar capitalisation throughout, identify the lack of 00:00 data

Add a (grey?) bar to indicate weekends for easier understanding of the chart timeframe.

Chart zoomed area is not drag-able on iPhone 4.

Data selection box resets position and size after adding a new sensor

Implement a caching system for sensor data files, to avoid fetching the data more than once. ~20k per sensor file, max of 50 for ~1MB maximum?

Add year to dropdown box timeframe selection for clarity.

Scale to fit and zoom options on main page produce errors with no sensor selected, and do not affect the plot's scale when one or more sensor plots are displayed.

When data is missing or not the length of others notify the user

Clicking the headers in the table would result in a sorted list below

The panel used for overall dataset plotting and controlled the focus zoomed plot's data uses only the first sensor selected, and is in the wrong colour.

Create nice looking site for tools etc and api docs etc!

When first sensor is a smaller data set than the second, adding the seconds data to the first breaks as the array is not big enough.

Use separate nodes for Average (information) and sensors (data, and or navigation).

Possible Triangles for nodes with children, Crosses for nodes with no clickable action (Average info) and squares for graph-able sensors

Mac style spinner in the graph div, or in a top corner.

Changing sensor layout can lead to inserting a sensor with a non-unique id and crash Slick grid

Info panel showing the number of sensors, the granularity of the data, a chart of the sensors by location, total build use last month, average building use, max and min overall. hall of fame- top 5 biggest users of power this month, total power use right now.

Possible carbon output etc too?

Instead of room location field.

Reset to the initial position

Plot colours should be a pool of available colours, not a fixed array.

The addition of a button that would remove all other plots apart from the selected one, but not change the view scale or size etc, to enable a user to clearly see individual plots that may be clouded by others.

Selection box uses position on page, not actual data selected to remember position.

In geography tree, in room GN17 and both top power are the same sensor, and is skewing averages etc.

Adding a new sensor shouldn't reset the view back to the initial selection

Fix totals in tree by changing energy to average power units, and specify what time frame the average was calculated over.

For data series that occur at different times, graphing chart will only chart up to the first dataset's cutoff, even if other data extends past this point.

Add one-time notification for displaying Alpha status of the tool.

Change columns in the table to show colour and total energy selected, and change average kW Total to Average kW in timeframe. Add double height top bar to Selected and Timeframe data.

Average calculation after initial sensor read could well be off - caware.util.js sumAverages only adds a new average?