Closed agrignard closed 4 years ago
Hi Arnaud,
brix
, I can change thatcityio_numeric_indicator
as a constructor of simple numeric indicators (e.g. average, max, count, etc). cityio_numeric_indicator
actually inherits from cityio_agent
. It is not necessary, but it might prove useful so we can leave it. is_heatmap<-true
@crisjf great job for the doc! it's great. I have some thought that we can discuss here
At the end shouldn't we call or
block
speciesbrix
? to be coherent? I find it confusing for the user to make the distinction between block and brix In https://cityscope.media.mit.edu/docs/modules/GAMA/#setup Do we still need cityio_numeric_indicator ? Now everything is in cityio_agent isn't it?In https://cityscope.media.mit.edu/docs/modules/GAMA/#basics-of-building-a-cityscope-indicator-in-gama An indicator will basically take in the properties of the block agents in the world=> an indicator can also be independent of the block no? e.g the mean age of each agent? aybe we should explain from the beginning that the GAMA module can compute indicator from the grid it self like brix at the end but more importantly can generate indicator from a simulation
In https://cityscope.media.mit.edu/docs/modules/GAMA/#gamabrix-for-cs-brix-users While brix can handle multiple tables at the same time by creating multiple threads for each Handler, GAMA is constrained to one table per model.=> should we work on that?
In https://cityscope.media.mit.edu/docs/modules/GAMA/#building-an-indicator-output is_heatmap<-false.=> true?
After https://cityscope.media.mit.edu/docs/modules/GAMA/#full-module-example-with-comments maybe can be nice to have a screenshot of how it look in the FE?