Open dunland opened 2 years ago
~lasert @cqx931 noch einen Slider + ein Grid~
@cqx931 :
@dunland:
[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)
sieht gut aus! :top:
@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;
@cqx931:
Infoscreen and frontend should be programmed according to this scheme:
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
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!
hey @kazux2 , here is a summary of some tasks for you:
@dunland @kazux2 :
scenario_A.csv
data/buildings_clusters.csv
seed
variable in the xml "Simulation Header", instead of listing it as a parameter
)2022-05-30
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
example: heat_connection as Pie-Chart @kazux2 (use gama-generated tables by @lwinkeler)
csv_export_test.csv
; located in Seafile/Q-Scope_data/includes/csv_exportexternalize questionnaire to another online-document
First version for testing has been created.
Accessible under: https://www.surveylegend.com/s/486i
Connected QR-Code:
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.
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:
[ ] 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:
[x] verify this: https://github.com/quarree100/q100_abm/issues/67
~input scenarios layout update?~
[x] input households: Gruppierungsmethoden?
"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
}
],
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[ ] 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
[x] https://github.com/quarree100/q100_abm/issues/76#issuecomment-1262242033: Zeitreihen für unveränderte Bestandsgebäude
@lwinkeler weil du dir bei der Übergabe Notizen gemacht hast, die hiermit veraltet sind:
since https://github.com/quarree100/qScope_frontend/commit/a684c717a21b492f22c3a35bd9376131972aa239:
--refurb [INT]
oder -r [INT]
ist jetzt int
mit Jahreszahl der Sanierung (merke: für alle vorausgewählten Gebäude)