weekly tasks & progress

[dunland]

• [x] slider position outside of grid
• [x] slider controls → cspy→q100_viz→infoscreen
• [x] 4-pin-LED-power + runde 2fach-Pinheader

[dunland]

KW 52 / später

~lasert @cqx931 noch einen Slider + ein Grid~

[dunland]

2022-KW1

@cqx931 :

• [x] Slider-Bereich einfärben je nach ausgewähltem Slider-Parameter
• [x] Infoscreen: Statusanzeige von Strom/Gas-Anbieter, Wärmenetzanschluss, Ausbau Technologie?

@dunland:

• [x] Besorgung LED-Stromquelle mit 4-Pin-Anschluss

[cqx931]

• [x] CO2-Emission

• [x] Stromverbrauch (erstmal generisch [0...1000]) → schlussendlich wohl anonym/randomisiert

• [x] Strom/Gas (herkömmlich/grau-grün/grün)

• [x] Wärmenetzanschluss (nein/ja)

• [x] Investition (Stufe 1 / Stufe 2 / Stufe 3 inkl. Wärmenetzanschluss / Stufe 4 inkl. Wärmenetzanschluss)

[dunland]

sieht gut aus! :top:

[dunland]

KW 03

@dunland:

• [x] NAT nachlesen + ABM verstehen → selber nochmal überlegen, was auf den Infoscreen gehört, also Visualisierungskonzepte → Mockup infoscreen ~(generell: buildings → households in q100_viz)~

  float CEEK; // Climate-Energy-Environment Knowledge
  float CEEA; // Climate-Energy-Environment Awareness
  float EDA; // Energy-Related-Decision Awareness
  float KA; // ---Decision-Threshold---: Knowledge & Awareness
  float PN; // Personal Norms
  float SN; // Subjective Norms
  float PSN; // ---Decicision-Threshold---: Personal & Subjective Norms
  float PBC_I; // Perceived-Behavioral-Control Invest
  float PBC_C; // Perceived-Behavioral-Control Change
  float PBC_S; // Perceived-Behavioral-Control Switch 
  float PBC_I_7; // Perceived-Behavioral-Control Invest divided by 7
  float PBC_C_7; // Perceived-Behavioral-Control Change divided by 7
  float PBC_S_7; // Perceived-Behavioral-Control Switch divided by 7  
  float N_PBC_I; // ---Decicision-Threshold---: Normative Perceived Behavioral Control Invest
  float N_PBC_C; // ---Decicision-Threshold---: Normative Perceived Behavioral Control Change
  float N_PBC_S; // ---Decicision-Threshold---: Normative Perceived Behavioral Control Switch
  float EEH; // Energy Efficient Habits
  
  int income; // households income/month -> ATTENTION -> besonderer Validierungshinweis, da zufaellige Menge
  string id_group; // identification which quartile within the income group the agent belongs to
  
  int age; // random mean-age of households
  int lenght_of_residence <- 0; //years since the household moved in
  string ownership; // type of ownership status of households
  string employment; // employment status of households !!!
  
  // defines network behavior of each agent in parent species by employment status
  int network_contacts_temporal_daily <- -99; // amount of agents a household has daily contact with - 30x / month
  int network_contacts_temporal_weekly; // amount of agents a household has weekly contact with - 4x / month
  int network_contacts_temporal_occasional; // amount of agents a household has occasional contact with - 1x / month
  int network_contacts_spatial_direct; // available amount of contacts within an households network - direct neighbors
  int network_contacts_spatial_street; // available amount of contacts within an households network - contacts in the same street
  int network_contacts_spatial_neighborhood; // available amount of contacts within an households network - contacts in the same neighborhood
  int network_contacts_spatial_beyond; // available amount of contacts within an households network - contacts beyond the system's environment TODO
  
  bool family; // represents young families - higher possibility of being part of a socialgroup
  bool network_socialgroup; // households are part of a social group - accelerates the networking behavior
  
  list social_contacts_direct;
  list social_contacts_street;
  list social_contacts_neighborhood;
  list social_contacts;

• (Kommunikationsstrukturen: Felder in buildings? )
  • (contacts: list of neighbors)
  • (draw lines / "send packages" between neighbors)
• (Kommunikationsstrukturen: Mockup für Kommunikationsstrukturen)
• [x] step-based simulation
  • [x] "simulating the simulation"
  • [x] (receive simulation-step from GAMA)
• [x] how to switch between the modes via TUI?

@cqx931:

• [x] q100_info an 4K-Monitor testen
• [x] infoscreen: metadaten ergänzen, falls noch welche fehlen
• [x] akkumuliertes CO2 (Cluster) anzeigen
• (plot: overall awareness change)
• (plot: overall energy grid efficiency)

[dunland]

Infoscreen and frontend should be programmed according to this scheme:

[cqx931]

https://github.com/cqx931/q100_info/commit/636e30c9bb29643acc77efd690959c6dba9f070

Um in den neuen Simulationsmodus zu sehen, drück die Leertaste. Für Quatier Simulation, habe ich erst mal ein paar "fake data" benutzt.

8

[dunland]

mhm, kannst du mir dafür vielleicht noch deine mockup daten zukommen lassen? Finde es nicht ganz einfach das nachzuvollziehen ohne die Inputdaten. das wäre sehr cool!

[dunland]

hey @kazux2 , here is a summary of some tasks for you:

• [x] get qScope_infoscreen and qScope_frontend to run!
• understand basics of node.js and d3.js
• dive into the Code of the infoscreen and understand what's going on. Please add Code documentation along the way.. the Code is quite spaghetti, and it would help a lot if the different sections were marked.
• [x] more specifically, take care of the line chart implementations in d3.

[dunland]

@dunland @kazux2 :

• [x] meetup feb-15 at 13:00 for a code kickstart
• @dunland get more info on what graphs to use
• [x] laser a "half-grid" and see how it's going..
• [x] we might need another "full grid" then, too (as long as we are only using 2 sliders)

[dunland]

KW22-24

Questionnaire Mode

• the questionnaire mode will (most likely) be excluded due to privacy issues → do we need another useful demo/introduction mode?
• infoscreen layout: 4 columns? / some loading screen ("X% questions answered")... @dunland @lwinkeler @kazux2
• [x] how to handle privacy issues? @dunland @lwinkeler → externalize questionnaire to another online-document @lwinkeler

Input Scenarios

1. [x] position the images
   • [x] dynamically resizable by canvas_size
   • later: dynamically resizable by grid size? should be e.g. 0.81 * canvas_width
2. [x] image: toggle selection
3. [x] UI: select by placing token on grid
   • [x] select by relative grid position? (1/2 vs 2/2)
4. [ ] what should infoscreen look like?
   • [x] send picked scenario handler to infoscreen ['A', 'B', 'C', 'D']
   • display more than just the variable names: what do these values imply @lwinkeler .. it would probably be good to make use of graphs and images here, later, too..
   • later: what should UI look like? → add to projection
5. [ ] display details on infoscreen @kazux2
6. how to leave this mode?
   • [x] global "ready" token..

• TODOS:
  • [x] rename "environment" -> "scenarios" @dunland
  • [x] update scenario csvs @dunland

Input Households

1. Interaction Possibilities: @lwinkeler
   • [x] set refurbishment
   • [x] drop parameter electricity supplier and environmental engagement for Q-Scope 1.0! @dunland
   • [x] set connection_to_heat_grid
   • [ ] token effect range per user:
     • [ ] link magnitude to ID of used token
     • [ ] A: using grid... how to handle rotation?
     • [x] B: polygons in range
       • [ ] now using rect.. use circle instead?
     • [ ] C: using address data (all in street / neighboring house numbers / ...)
     • [ ] apply effect to parameter of buildings in range
   • [ ] "ready" button per user
2. Infoscreen:
   • [ ] Display the selected scenario (human-readable short name) somewhere @kazux2 @lwinkeler
   • [ ] layout concept: how many buildings possible per column? need of aggregated/average values? @kazux2 @dunland
   • [ ] layout realization: display selected buildings column-wise (one column for each user) @kazux2

3. 33

Simulation Mode

• [x] select scenario data → use it to compose GAMA-dataframe! ... use, for example scenario_A.csv
• [x] export building cluster json as csv for GAMA to read @dunland ... is exported as data/buildings_clusters.csv
• [x] making GAMA run via headless mode @dunland
  • [x] adjust frontend-code for this procedure: create xml accordingly (by including the seed variable in the xml "Simulation Header", instead of listing it as a parameter)
  • [x] create a routine to allocate frontend-adjusted buildings-parameters to agents in GAMA @lwinkeler see q100abm/issues/56
    1. run gama, wait for it to finish
    2. receive / read data
    3. pass variables to infoscreen, enter data view

Data View

2022-05-30

• [x] Infoscreen: enter data view mode
• [ ] example: heat_connection as Pie-Chart @kazux2 (use gama-generated tables by @lwinkeler)
• [ ] example: heat_connection and emissions as f(t) @kazux2

[lwinkeler]

infoscreen layout: 4 columns? / some loading screen ("X% questions answered")...

• see Seafile/Medias-in-RES_intern/q100-qScope/Data/Erhebungen/Erhebung_2022-nachNiamir for questions (especially green highlighted ones)
• possible answers / scale should also be included

display more than just the variable names: what do these values imply

• see Seafile/Q-Scope_data
• files scenario A / B / C / D
• column "name_human_readable" & "value_human_readable"

Display the selected scenario (human-readable short name) somewhere

• see Seafile/Q-Scope_data/scenario_titles.csv
• [ ] should be discussed

[lwinkeler]

example: heat_connection as Pie-Chart @kazux2 (use gama-generated tables by @lwinkeler)

• gama model on main branch now exports csv file with columns of cycle, date and transformation level
• transformation level changes every year and represents refurbished houses -> share of houses within the neighborhood that are connected to heat grid
• file name: csv_export_test.csv; located in Seafile/Q-Scope_data/includes/csv_export

[lwinkeler]

externalize questionnaire to another online-document

First version for testing has been created.

Accessible under: https://www.surveylegend.com/s/486i

Connected QR-Code:

[dunland]

example: heat_connection as Pie-Chart @kazux2 (use gama-generated tables by @lwinkeler)

* gama model on main branch now exports csv file with columns of _cycle_, _date_ and _transformation level_

* _transformation level_ changes every year and represents refurbished houses -> share of houses within the neighborhood that are connected to heat grid

* file name: `csv_export_test.csv`; located in _Seafile/Q-Scope_data/includes/csv_export_

The naming of the columns in this file is not intuitive and problematic. The last column should have a simple name like "value", for example. We will look into this once we deal with what outputs GAMA shall generate.

[dunland]

2022-KW29

TODO @dunland

• [x] ABM push überprüfen

• [x] send sum of connections per group

• [x] wrap "data_view_data" around json struct + get rid of [ ] in json

• [x] combine the two messags sent for dataview

• [x] dataview infoscreen: fix multi-line-graph data messaging with kazu

• [x] token → select cell → select ALL buildings (opt)

• [x] infoscreen dataview: Dateinamen von Emissions%20per%20yearnull.png anpassen (s. GAMA)

• [x] infoscreen households input: only show selected buildings! where do the others come from? maybe has to do with viz.js:399:11:

  Object { connection_to_heat_grid: 0, group_0: {…}, group_1: (3) […], group_2: (3) […], group_3: (3) […], year: 0 } connection_to_heat_grid: 0 group_0: Object { connections: 0, buildings: (2) […] } group_1: Array(3) [ 0, 1, 2 ] group_2: Array(3) [ 0, 1, 2 ] group_3: Array(3) [ 0, 1, 2 ]

• [ ] infoscreen households input:

  • [x] get the layout right! → align buildings to top
  • [ ] fixed width
  • [ ] header and color code for groups

• [ ] simulation mode: what happened to "simulation is running" infotext?

• [ ] simulation/GAMA-API: change path of buildings_clusters.csv, using timestamp + add buildings group to API

• [ ] input buildings:

  • [ ] rotation to change parameters?
  • [ ] color selected buildings according to user

• [x] verify this: https://github.com/quarree100/q100_abm/issues/67

• [ ] https://github.com/quarree100/q100_abm/issues/76

• ~input scenarios layout update?~

• [x] input households: Gruppierungsmethoden?

[dunland]

2022-KW32

simulation-mode

• [ ] start new process (using multiprocessing!) for simulation; display "simulation is running"

infoscreen

• [x] Umsetzung Layout von R+E
  • [x] Prüfen eingegangener Vorschläge von Nele:
    • [x] Definition unserer Workshop-Ziele
    • [x] Decken sich diese mit den Vorschlägen?
• [x] programming the graphs using matplotlib → probably much faster than d3...
  • [x] results, total: CO2-Ausstoß des Quartiers
  • [x] results, individual: CO2-emissions per user group
  • [x] beautifications: replace date construct by german-format date e.g. like this

hardware

• [x] 3D-prints of tokens! @kazux2
• [x] setup offline version by downloading all necessary js packages

[dunland]

2022-KW33

interaction @dunland

• [x] lines that show heat grid connection
• ~global slider for game stages and modes:~
  • [x] introduce new handles in grid .csv files
  • ~remove mode selector tokens~
  • [x] cspy_L needs second slider:

    "sliders": [
    {
        "id": "slider0",
        "step_size": 0.01,
        "x_min": 85,
        "x_max": 775,
        "y": 972
    },
    {
        "id": "slider1",
        "step_size": 0.01,
        "x_min": 1000,
        "x_max": 1500,
        "y": 972
    }
    ],

[dunland]

2022-KW34

Fr

• [x] https://github.com/quarree100/qScope_frontend/issues/37
  • [x] Kategorisierung der Gebäude nach ['year', 'energy_source', 'area']
  • [x] stattdessen: Kategorisierung über die Verbrauchsdaten; entweder nach Range oder festen Grenzen
• [ ] edit LW: Berücksichtigung der NWG (bspw. von Beginn an eigener Cluster)
• [x] individual data view: neues Layout
• [x] individual data view: mockup json-struct → Kazuki schicken

Sa/Mo

• ~Schleife zurück zu Szenarieneingabe: Wie soll das nun aussehen?~
• [x] include input_scenarios to input_households → rename "interaction_mode": scenarios as integrated part of this mode. first step: setup scenarios (use global slider?)
• [x] welche Parameter sollen nun angepasst werden?? Energiekosten + Finanzkonzept + Anschlussquote
• [x] rename sliders in cspy/settings/qscope_X.json consecutively (grid 1: slider0, slider1; grid 2: slider2, slider3)

[dunland]

2022-KW35

Interaction

• [x] Interaction mode: layout infoscreen (approximately same as individual data view)
• [x] interaction mode: include clustered energy data of building
• [x] time line with mode selectors instead of slider for game mode
• [x] global slider to define number of (other) buildings to connect

Ergebnisdarstellung

• [x] ABM-Feature: tranquilize agents ASAP, Ende KW35 @lwinkeler
• [x] ABM: building-specific energy prices https://github.com/quarree100/q100_abm/issues/82
  • [x] → individual data view: create graphs via matplotlib
  • [x] → individual data view: send graphs to infoscreen
• [x] switch between modes: individual and total data view

[dunland]

2022-KW41

Interaction

• [x] infoscreen: highightling selected decsion feature + coloring buildings according to connection status @kazux2 https://github.com/quarree100/qScope_infoscreen/issues/27
• ~frame around infoscreen in color of current round~

individual data view:

• [x] verify buildings ø-consumption data
• [x] round-based graph layers? → pass decisions of round as string to graph legend
• [x] display cluster_size

UI

• [x] slider: show thresholds for non-bools / two-colored codes

---

Extensions

• [x] Anschlusszeitpunkt: https://github.com/quarree100/q100_abm/issues/83
• [x] discuss environmental_engagement https://github.com/quarree100/qScope_infoscreen/issues/23#issuecomment-1229962529 (bool vs float vs string) + implement: https://github.com/quarree100/q100_abm/issues/91
• [x] more comprehensive/static general mode-independent layout https://github.com/quarree100/qScope_infoscreen/issues/29

~Einführung~

• ~create Introduction mode~
• ~Überblick-Einstellung auf Infoscreen: zeige alle Stellschrauben / Parameter; hebe jene hervor, die wir ändern werden~

[dunland]

2022-KW43

Interaction

• https://github.com/quarree100/qScope_frontend/issues/34
• [x] Anschluss 2024-2040

Results:

• [x] Default-Werte (keine Entscheidungen) vorberechnen
• [x] Graphen: Energiekosten in Vergleich: gestrichelte vs durchgängige Linie
• [x] Energiezentrale weg

Hardware

• [x] test interaction/light conditions with many people around table

---

Extensions

• ~Skalierung der Nutzerentscheidungen pro User/Slider?~ nein, weil Einflüsse in den Ergebnissen schwer zu entschlüsseln wären
• ~slider value averaging?~
• ~frame around infoscreen for iteration round: https://github.com/quarree100/qScope_infoscreen/issues/28~

[dunland]

2022-KW44

Interaction

• [x] https://github.com/quarree100/qScope_frontend/issues/41
• [x] tableAddRow erst wenn wieder zurück in buildingsInteraction
• [x] undo clustering, use consumption data rightaway to display the according graph https://github.com/quarree100/q100_abm/issues/92#issuecomment-1283587649

Simulation

• [x] show some graphs for discussion here while simulation is running

Results:

• [ ] Ergebnisse überprüfen und validieren!!! https://github.com/quarree100/q100_abm/issues/76

• [ ] make graphs more comprehensive: https://github.com/quarree100/qScope_frontend/issues/39

• [ ] Graphen: deutlichere Farben pro Runde

• [x] Graphen: gleiches ylabel min([ymin]), max([ymax]) ??

• [x] https://github.com/quarree100/qScope_frontend/issues/42

  individual data view:

• [x] https://github.com/quarree100/q100_abm/issues/76#issuecomment-1262242033: Zeitreihen für unveränderte Bestandsgebäude

total data view

• [ ] Infoscreen: Spalte rechts für Haushaltsentscheidungen?

UI

• [x] :exclamation: https://github.com/quarree100/qScope_infoscreen/issues/30
• [ ] (Adressen auf Frontend?)
• [ ] Piktogramme für Slider! + Infoscreen
• [ ] historische Energiepreise sollen zumindest als Backup für Rückfragen zur Verfügung stehen! Kür: historische Daten an Individualgraphen voranstellen
• [ ] frame slider area according to user color

Hardware

• [x] :exclamation: color building tokens according to groups
• [x] :exclamation: laser cutting of 3 slider middle parts

---

Extensions

• [ ] display scenario: Finanzierungskonzepte https://github.com/quarree100/q100_abm/issues/88
• [ ] add tooltips on infoscreen https://github.com/quarree100/qScope_infoscreen/issues/24
• [x] https://github.com/quarree100/qScope_frontend/issues/30#issuecomment-1225686374
• [ ] Quartiersdarstellung aus GAMA auf Frontend anzeigen?
• [x] Zeitverläufe vor 2020 ? Achtung: Berücksichtigung Inflationsrate, ....
• [ ] show share of different energy_sources in neighborhood (gas, oil, q100); e.g. before/after simulation https://github.com/quarree100/qScope_infoscreen/issues/23#issuecomment-1234246567

[dunland]

Updates

@lwinkeler weil du dir bei der Übergabe Notizen gemacht hast, die hiermit veraltet sind:

since https://github.com/quarree100/qScope_frontend/commit/a684c717a21b492f22c3a35bd9376131972aa239:

• keys for corner point selection in calibration mode are 1,2,3,4 (not TAB - analog zu cspy)
• game Modes can be switched via 0,9,8,7
• flag --refurb [INT] oder -r [INT] ist jetzt int mit Jahreszahl der Sanierung (merke: für alle vorausgewählten Gebäude)