16_ “Green” charging E-Mobility

When is it “greener” to charge an electric car?

People1 Posts42 Dribs40

Event finish

Edited

3 years ago ~ martin_baldinger

Repository updated

3 years ago ~ martin_baldinger

Output nicer graph from Martin's work

made some analysis on how the co2 intensity looks like on a per day and hour basis (@martinbaldinger-ekz)

Merge remote-tracking branch 'origin/main' into main

made some analysis on how the co2 intensity looks like on a per day and hour basis

Add notebook to merge in CO2 values to meter energy consumption

Edited

3 years ago ~ martin_baldinger

all systems go

3 years ago ~ martin_baldinger

Add files via upload

Merged the two metervalue files and deleted all charge_log_ids with at least one increment > 5500. (@fabiofuerst)

Edited

3 years ago ~ martin_baldinger

Joined the team

3 years ago ~ martin_baldinger

Merge branch 'main' of https://github.com/invveritas/green_charging_emobility into main

Update Merge meter with CO2 data.ipynb

bugfix (@martinbaldinger-ekz)

replace NaN Chargepoints in Notebook template.ipynb

replace NaN Chargepoints in Notebook_Martin.ipynb

Merge remote-tracking branch 'origin/main' into main

replace NaN Chargepoints in Notebook_Martin.ipynb

Update readme with CO2 dataframe labels

Merge branch 'main' of https://github.com/invveritas/green_charging_emobility into main

Create Merge meter with CO2 data.ipynb

added units for carbon intensity file to README.md (@martinbaldinger-ekz)

Merge branch 'main' of https://github.com/invveritas/green_charging_emobility into main

Create Template with joined clean meter data.ipynb

data clean-up guideline for increments > 5500: remove the whole charge_log_id (@martinbaldinger-ekz)

Add note on maximum charging

Add template notebook

Add data directory

Update readme with coding standards

Create .gitignore

Merge pull request #5 from cmutel/patch-1

Update README.md with data format

Update README.md

Initial commit (@invveritas)

Start

Edited

3 years ago ~ Maud

Challenge shared
Tap here to review.

3 years ago ~ Maud
All attendees, sponsors, partners, volunteers and staff at our hackathon are required to agree with the Hack Code of Conduct. Organisers will enforce this code throughout the event. We expect cooperation from all participants to ensure a safe environment for everybody. For more details on how the event is run, see the Guidelines on our website.

Creative Commons LicenceThe contents of this website, unless otherwise stated, are licensed under a Creative Commons Attribution 4.0 International License.