Dominik Moritz
Dominik Moritz
Would be good to show an embedding visualization of Draco specs using the feature vectors of constraint violations.
Right now, Draco's default model implements effectiveness as the optimization criterion. One can easily provide other weights but we could make it easier and clearer how to add new metrics...
For #730 Doesn't quite work. ``` draco/asp/generate.lp:6:1-85: error: unsafe variables in: 0
- [ ] Consider using defaults - [ ] Remove `not_required` and just use `not required` - [ ] Use unsat cores to find minimal sets of violations - [...
See https://readthedocs.org/dashboard/draco2. I already set up sphinx. Maybe we need something like https://github.com/astrojuanlu/jupyterbook-on-read-the-docs/blob/main/.readthedocs.yaml.
Dziban combines Draco+GraphScape. It would be great to support it in Draco2.
See "GEViTRec: Data Reconnaissance Through Recommendation Using a Domain-Specific Visualization Prevalence Design Space". The idea is to find the graph of connected fields and then to generate possible charts in...
* When y becomes too small, instead use color. E.g. relevant for faceted line charts that become lasagna plot. * Prefer stacking when the data is ratio.
Clorm is an ORM for ASP. It could make Draco's code easier: https://clorm.readthedocs.io/en/latest/clorm/predicate.html.