openenergydashboard / oed Goto Github PK
View Code? Open in Web Editor NEWOpen Energy Dashboard (OED)
License: Mozilla Public License 2.0
Open Energy Dashboard (OED)
License: Mozilla Public License 2.0
need to get admin tool working so can set up for others. Once done notify DB team to set up tables.
We currently read them by the hour but our system should be able to handle the extra data.
The current system works but as we make progress on the project changes should be made and incorporated.
We need first-class responsive mobile support, including placing the options for manipulating the graphs in a way that works on mobile. This is going to require some discussion about what we want the site to look like on a phone.
Create a nice way to import new meter data.
We have enough actions types now that we need to make a conscious effort to make their names distinctive. The type definitions are also creating large blocks of boilerplate at the tops of files.
Factoring out the action type definitions into a dedicated file should help with both of these issues.
Set up a demo to show collaborators and establish a front end framework to use going forward.
We need to be able to compare and normalize readings in order to support things like competitions between buildings or to compare energy usage from different periods in time.
We're currently sending every data point to the server, which is crashing the browser after about 2000 points. We need to condense the points before we send them.
Getting Tableau working with the database may have left some potential security holes on our server. Fix them.
Set up an API so that frontend has something to work with.
Standardize tools and workflow
Do any users need to be able to set their data resolution explicitly? If so, do they need to be able to set a minimum resolution (e.g. at least 1 point per given time period) or an exact resolution? How would that work?
Create back-end testing with Mocha and Chai.
Implement a way to inform the user when things happen.
Actual meter names may have been changed since the beginning of the logs, need to find any that have. Also, need to match logs to their meter they're from and identify which aren't from a current meter name. Also also, we're not posting the shareable link to the data publicly, so I have that for you if you're working on this.
The admin panel should allow admins to import new meters, create/edit/view groups, and any other administrative duties.
There has already been some work done on this, located in the "adminPanel" branch.
Add legacy MAMAC readings to db
Our testing doesn't have E2E tests working yet, getting Protractor up will let us write these tests.
Find and detect gaps in data.
The Readme file has a link to a CLA in the contributions section. Clicking on that link produces the following error message: You need permission
This form can only be viewed by users in the owner's organization.
Try contacting the owner of the form if you think this is a mistake. Learn More.
We need to display properly on multiple types of screens.
meterCron.js is a leftover from early testing. We should duplicate the functionality in a way that makes more sense in the long term.
Currently when the user changes which meters are selected, we fetch readings for both line and bar charts. This will be efficient if users switch between line and bar chart for the same meters more frequently than they switch between meters within a graph type. I do not think this will be the case. Until there is some reason to believe otherwise, I think a single user action should dispatch as few API requests as possible. This was briefly discussed in re #85, and I think we came to the wrong conclusion.
Discover why the crash happened and try to make the program more resilient.
Implement Grouping
Figure out how to back up our postgres db.
Add some dummy data to see if our system will be able to serve up charts as quickly in the future.
Under "Licensing" the readme states that the project is licensed under the GPL v3. We should change this immediately.
Some of the sql queries for retrieving meters didn't get the extra columns added when we added more fields to the meters table. As a consequence, some meters have undefined type and status after they are returned from the database.
Much of the code needs to be documented to allow for ease of understanding.
Look into adding internationalization support to the software.
Design problems:
Create a UI to add, remove, and edit groups.
I was thinking that maybe we should change the repository name. First, JS is probably not needed and is not the only technologies used. Second, ED is not as descriptive so should we spell it out? An alternative is to add topics so it is easier to find. I think we should do this before it goes public.
This issue has been seen on one personal computer and on the OED server.
The problem is requests to the API returning the source of index.html
instead of the requested data, causing an error in the frontend when data.map
is not a function.
The cause appears to be some thing to do with the Express routing setup in src/server/app.js
. In line 32 of app.js
, we have:
app.get('*', (req, res) => {
res.sendFile(path.resolve(__dirname, '..', 'client', 'index.html'));
});
This block is intended to forward routing except API requests to react-router on the client. The issue is that requests that should be sent either to an API or to an error handler are instead being handled by this logic and getting index.html
. The APIs with which we've had this problem have been registered with the API middleware above this block in app.js
.
Changing the *
to a /
so that the code reads:
app.get('/', (req, res) => {
res.sendFile(path.resolve(__dirname, '..', 'client', 'index.html'));
});
appears to fix the problem, but the strange thing is that changing it back to a *
does NOT cause the issue to reappear.
If you run into this issue pay attention to what's going on and reply to this issue with relevant details.
Interpret the data in terms of cost.
Parallel to #57. Allow graphing between groups (each group is represented in aggregate) or within groups (each meter in a single group is represented individually).
Design questions:
Initially, focus should be on comparing groups with each other.
Winston was set up on a test branch a while back but due to the substantial changes to the code since then it should be reimplemented and added to master.
Before going open source we need to clean up the repo so that Beloit specific things aren't cluttering the repo.
We should figure out how to support https, esp. as we develop login/admin
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.