• Functions to allow overridable integration of results
• Use protoc insertion points
• Calin specific option to control default implementation

Add numeric differentiation class

Must check oneof for all fields along path!

Add ability to read from old files into protobufs that have new fields added

Allow new fields and tables to be added to existing DB

Write SWIG interfaces directly from protoc?

Not looking forward to this one.

Write helper function to fit functions to histograms

Find out cause of random exceptions from NLOpt with exp gauss models. Catch exceptions in callback and print

Calculate hessian by finite differences from gradient and from function itself

As in title

Like it says in the title

Implement HDF reader and writer using old ChiLA helper classes, possibly as extension to protobuf compiler

Could allow:

1. Freeze and thaw of axes - frozen axes become parameters
2. Transformation to log of specified axes?

Could this be solution?

https://cmake.org/cmake/help/v3.4/policy/CMP0060.html

Start Python interface with SWIG. Try some different ways to lat out modules. How to handle protobufs??

Add clone member to ask function types so that a multi thread adapter could make copies that would operate in different threads without interfering with each other

See comment in : VSORayTracer::trace

Investigate the open source options for CI. TravisCI? See matt's project

Return OIDs of found entries

• should allow multiple outputs
• one of these should use Python O/P to allow printing into ipython notebooks
• think about locking

Choose documentation system (doxygen?) and start to document classes

Allow for specifying a(0) rather than b(0) and also allow setting of these parameters for last point rather than first

• Why do we need to "select_inherited_keys" ?
  • where would they come from and
  • where in general would we store them (if we were selecting from the subtree)
• Don't select OID when it's provided
• Why do we really need to select parent_oid? What would we do with it anyway?

Need to re-understand what the problem is and fix it. See comments in:

VSOMirror::mirrorToReflector
VSOMirror::reflectorToMirror

• add binsize correction to normalization in set_cache
• fix bin centering in general spe

Write a class to serialize protobuf messages to sqlite and mysql using reflection

Add code to do likelihood profile and MINOS errors

Add telescope event simulator to use for unit tests

Get rid of map for oneof but rather use message directly

Warn if norm drifts too far. Also allow correction of norm (bu disallow gradients)

Discard upward going tracks, or those too distant from telescopes etc

Faster and better

Decide on a threading policy and add threading constructs where appropriate - eg in spe_likelihood

Should be dx_(isegment)

• Do not use fully qualified name unless necessary
• Allow inherited keys to be imported with original names if possile
• Allow imported inline fields to have original names if possible