Carleton Coffrin

v0.8.1 @JuliaRegistrator register()

v0.8.2 @JuliaRegistrator register()

Add a test where all possible components are omitted, e.g. no shunts, no transformers. And make sure to test the `write_solution1` and `write_solution2_contingency` functions.

Add tests for output of shunt control parameters in `write_solution1` and `write_solution2_contingency`.

It is possible that `constraint_power_balance_shunt_dispatch_soft` could be removed. In other cases, tests should be written to increase coverage.

I had the same issue doing a fresh install in 0.5.2. It seemed to be resolved by removing the `CoinOptServices` and `AmplNLWriter` packages and then reinstalling them, with `CoinOptServices` coming...

An attempt collect solver callback documentation. **Significant Callback Support** - [Gurobi](https://www.gurobi.com/documentation/7.0/refman/callback_codes.html) - [CPlex](https://www.ibm.com/support/knowledgecenter/en/SSSA5P_12.6.2/ilog.odms.cplex.help/refpythoncplex/html/cplex.callbacks-module.html) - [SCIP](http://scip.zib.de/doc/html/EVENT.php) - [Express](http://www.fico.com/en/node/8140?file=5097) - [Mosek](http://docs.mosek.com/7.1/javaapi/Callback_objects_and_related_functions.html) - [Knitro](https://www.artelys.com/tools/knitro_doc/2_userGuide/callbacks.html) - GLPK (in PDF available [here](https://www.gnu.org/software/glpk/glpk.html)) **Minor/Unclear Callback Support**...

Notes from meetup discussion, - we will not attempt to generalize over callbacks, there is too much diversity in the solvers - we should try to design a clean callback...

@mlubin do you have thoughts on this approach? https://guides.github.com/activities/citable-code

I was googling into this and I found that it is indexing some things at least, https://scholar.google.com/scholar?as_publication=zenodo For example, https://scholar.google.com/scholar?cluster=15397132910898847372&hl=en&as_sdt=5,32&sciodt=0,32 Maybe a recent development? One thing that is a bit...