Comment by spyckie2
6 years ago
unfortunately, not really. The language you have to speak is still in variables, buttons and code.
I'd love to be able to write in a way that feels more like documenting models rather than writing code. Admittedly this is a really spoiled point of view since ideas are cheap but execution is hard.
A quick example is as follows:
Persons have stress level from 0-100, start with random stress, and belong in the following environment conditions:
Normal: Stress + 0 / year
Low Income: Stress + 5 / year
High Income: Stress - 5 / year
Change functions:
Every year, 0-3% persons change from low income to normal income
0-1% of persons change from normal income to high income
Population has 100 persons
Groups:
stress level > 50 is "high risk of heart attack"
stress level < 20 is "low risk of heart attack"
This kind of definition should be enough to chart out # of people in the high risk group over a period time.
What I imagine is writing more or less the above as psuedocode and then a framework to automatically scaffold a basic data view and controls for time / data manipulation.
edit i took a further look at idyll, and this language can probably be built on top of idyll.
psuedocode here https://gist.github.com/lifedispenser/3a9a3433551a324097829e...