If declare concepts but not variables (esp. data type), ask user for input rather than error out. --> Some kind of hook for checking and then asking for additional input.
Ex. When querying knowledge base, check that Variable is declared before verifying/solving. If Variable is not declared, interactivity
Elicit weights for edges that represent causes, correlations that want to include in the final statistical model and then maximize these?
Presenting differences between models (set of effects for each model may differ): Visual pattern matching (make similarities easy to look over, differences more prominent, something from NLP/error analysis lit?
Milestones for interaction:
Low fidelity pass for interactivity: command line interaction (pdb)
Implementation ideas:
Could we use the listener pattern somehow such that missing info is logged somewhere, updates to info are logged somewhere, etc.?
If declare concepts but not variables (esp. data type), ask user for input rather than error out. --> Some kind of hook for checking and then asking for additional input. Ex. When querying knowledge base, check that Variable is declared before verifying/solving. If Variable is not declared, interactivity
Elicit weights for edges that represent causes, correlations that want to include in the final statistical model and then maximize these?
Presenting differences between models (set of effects for each model may differ): Visual pattern matching (make similarities easy to look over, differences more prominent, something from NLP/error analysis lit?
Milestones for interaction: Low fidelity pass for interactivity: command line interaction (pdb)
Implementation ideas: