CalTRACK
Methods are developed in an open and transparent stakeholder process that uses empirical testing to define replicable methods for calculating normalized metered energy consumption using either monthly or interval data from an existing conditions baseline.
https://github.com/opendsm/caltrack
Category: Consumption
Sub Category: Production and Industry
Keywords from Contributors
building-energy efficiency energy-data energy-efficiency weather weather-data weather-station
Last synced: about 10 hours ago
JSON representation
Repository metadata
Shared repository for documentation and testing of CalTRACK methods
- Host: GitHub
- URL: https://github.com/opendsm/caltrack
- Owner: opendsm
- License: cc0-1.0
- Created: 2018-01-24T16:30:37.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2023-05-18T21:58:12.000Z (almost 2 years ago)
- Last Synced: 2025-03-09T00:03:17.802Z (about 2 months ago)
- Language: Dockerfile
- Homepage: http://docs.caltrack.org
- Size: 3.35 MB
- Stars: 56
- Watchers: 42
- Forks: 14
- Open Issues: 2
- Releases: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
README.md
CalTRACK Technical Documentation
CalTRACK methods are developed in an open and transparent stakeholder process that uses empirical testing to define replicable methods for calculating normalized metered energy consumption using either monthly or interval data from an existing conditions baseline.
This repository contains the CalTRACK 2.0 methods, and the CalTRACK Technical Appendix, which explains how many of the methods were developed.
Future improvements are catalogued as "Issues" and are found in the Projects tab. These issues are considered "closed" until they are formally re-opened by the Working Group.
Formal changes in methods will follow processes established under the JDF charter:
Deliverable Development Process
Working Groups. The Project may have multiple Working Groups, and each Working Group will operate as set forth in this Section and its Working Group Charter.
Working Group Chair. Each Working Group will designate a chair for that Working Group. A Working Group may select a new chair upon Approval of the Working Group Participants.
Working Group Requirements. Each Working Group must be comprised of at least 2 Working Group Participants. No Working Group Participant will be permitted to participate in a Working Group without first Joining the Working Group.
Conditions for Contributions. A Steering Member, Associate, or Contributor may not make any Contribution unless that Steering Member, Associate or Contributor is the exclusive copyright owner of the Contribution or has sufficient copyright rights from the copyright owners to make the Contribution under the terms of this Project Charter and applicable Working Group Charter. The Steering Member, Associate, or Contributor must disclose the identities of all known copyright owners in the Contribution.
Deliverable Development Process
Pre-Draft. Any Working Group Participant or Contributor may submit a proposed initial draft document as a candidate Draft Deliverable of that Working Group. The Working Group chair will designate each submission as a “Pre-Draft” document. This quick-start video shows how to submit an issue for consideration.
Draft. Each Pre-Draft document of a Working Group must first be Approved by the Working Group Participants of that Working Group to become a Draft Deliverable. Once the Working Group approves a document as a Draft Deliverable, the Draft Deliverable becomes the basis for all going forward work on that deliverable.
Working Group Approval. Once a Working Group believes it has achieved the objectives for its deliverable as described in the Scope, it will progress its Draft Deliverable to “Working Group Approved” status.
Final Approval. Upon a Draft Deliverable reaching Working Group Approved status, the Executive Director or his/her designee will present that Working Group Approved Draft Deliverable to all Steering Members for Approval. Upon Approval by the Steering Members, that Draft Deliverable will be designated an “Approved Deliverable.”
Publication and Submission. Upon the designation of a Draft Deliverable as an Approved Deliverable, the Executive Director will publish the Approved Deliverable in a manner agreed upon by the Working Group Participants (i.e., Project Participant only location, publicly available location, Project maintained website, Project member website, etc.). The publication of an Approved Deliverable in a publicly accessible manner must include the terms under which the Approved Deliverable and/or source code is being made available under, as set forth in the applicable Working Group Charter.
Submissions to Standards Bodies. No Draft Deliverable or Approved Deliverable may be submitted to another standards development organization without Approval by the Steering Members. Upon Approval by the Steering Members, the Executive Director will coordinate the submission of the applicable Draft Deliverable or Approved Deliverable to another standards development organization with Joint Development Foundation Projects, LLC. Working Group Participants that developed that Draft Deliverable or Approved Deliverable agree to grant the copyright rights necessary to make those submissions.
Owner metadata
- Name: OpenDSM
- Login: opendsm
- Email: [email protected]
- Kind: organization
- Description: Collaboratively advancing the future of demand-side energy
- Website: https://lfenergy.org/projects/opendsm/
- Location:
- Twitter:
- Company:
- Icon url: https://avatars.githubusercontent.com/u/19336002?v=4
- Repositories: 3
- Last ynced at: 2025-02-04T14:43:20.546Z
- Profile URL: https://github.com/opendsm
GitHub Events
Total
Last Year
Committers metadata
Last synced: 7 days ago
Total Commits: 267
Total Committers: 22
Avg Commits per committer: 12.136
Development Distribution Score (DDS): 0.745
Commits in past year: 0
Committers in past year: 0
Avg Commits per committer in past year: 0.0
Development Distribution Score (DDS) in past year: 0.0
Name | Commits | |
---|---|---|
matthewgee | m****e@g****m | 68 |
McGee Young | m****g@g****m | 48 |
Tom Plagge | t****e@g****m | 31 |
Matt Golden | m****t@e****g | 23 |
hshaban | h****n@g****m | 22 |
Blake Hough | b****e@B****l | 10 |
houghb | b****e@e****m | 10 |
Marc Pare | m****0@g****m | 9 |
Dave Yeager | d****r@o****o | 8 |
houghb | h****b | 7 |
Kevin Gries | 3****s | 5 |
Steven Chang | s****g@d****m | 5 |
Phil Ngo | 1****e | 4 |
Peter Olson | p****n@g****m | 4 |
Stephen Suffian | s****e@o****o | 3 |
CBestbadger | 3****r | 2 |
Tom Plagge | t****e@o****o | 2 |
Jon Farland | J****d@d****m | 2 |
Phil Ngo | n****l@g****m | 1 |
admin | a****n@M****l | 1 |
Matthew Gee | m****e@M****l | 1 |
Stephen Suffian | s****n@g****m | 1 |
Committer domains:
- openee.io: 3
- dnvgl.com: 2
- energysavvy.com: 1
- efficiency.org: 1
Issue and Pull Request metadata
Last synced: 1 day ago
Total issues: 94
Total pull requests: 6
Average time to close issues: 2 months
Average time to close pull requests: 18 minutes
Total issue authors: 9
Total pull request authors: 2
Average comments per issue: 4.27
Average comments per pull request: 0.17
Merged pull request: 6
Bot issues: 0
Bot pull requests: 0
Past year issues: 0
Past year pull requests: 0
Past year average time to close issues: N/A
Past year average time to close pull requests: N/A
Past year issue authors: 0
Past year pull request authors: 0
Past year average comments per issue: 0
Past year average comments per pull request: 0
Past year merged pull request: 0
Past year bot issues: 0
Past year bot pull requests: 0
Top Issue Authors
- hshaban (76)
- steevschmidt (8)
- philngo (4)
- jskromer (1)
- danrubado (1)
- mcgeeyoung (1)
- mtham8 (1)
- bkoran (1)
- eliotcrowe (1)
Top Pull Request Authors
- hshaban (5)
- philngo (1)
Top Issue Labels
Top Pull Request Labels
Dependencies
- sphinx * develop
- sphinx-autobuild * develop
- sphinxcontrib-spelling * develop
- typing * develop
- alabaster ==0.7.12 develop
- argh ==0.26.2 develop
- babel ==2.6.0 develop
- certifi ==2019.3.9 develop
- chardet ==3.0.4 develop
- docutils ==0.14 develop
- idna ==2.8 develop
- imagesize ==1.1.0 develop
- jinja2 ==2.10.1 develop
- livereload ==2.6.0 develop
- markupsafe ==1.1.1 develop
- packaging ==19.0 develop
- pathtools ==0.1.2 develop
- port-for ==0.3.1 develop
- pyenchant ==2.0.0 develop
- pygments ==2.3.1 develop
- pyparsing ==2.4.0 develop
- pytz ==2019.1 develop
- pyyaml ==5.1 develop
- requests ==2.21.0 develop
- six ==1.12.0 develop
- snowballstemmer ==1.2.1 develop
- sphinx ==2.0.1 develop
- sphinx-autobuild ==0.7.1 develop
- sphinxcontrib-applehelp ==1.0.1 develop
- sphinxcontrib-devhelp ==1.0.1 develop
- sphinxcontrib-htmlhelp ==1.0.1 develop
- sphinxcontrib-jsmath ==1.0.1 develop
- sphinxcontrib-qthelp ==1.0.2 develop
- sphinxcontrib-serializinghtml ==1.1.3 develop
- sphinxcontrib-spelling ==4.2.1 develop
- tornado ==6.0.2 develop
- typing ==3.6.6 develop
- urllib3 ==1.24.1 develop
- watchdog ==0.9.0 develop
- sphinx *
- sphinx-autobuild *
- python 3.7.0 build
- caltrack_docs_shell latest
Score: 7.151485463904735