Created TrajectoryReportToDB to enable use of the features reporter system for trajectory output
TrajectoryReportToDB is a child Mover of ReportToDB, meaning most of its functionality
is the same as ReportToDB (e.g. any existing features reporter can be used with it).
The new behavior is that the class counts how many times each pose (identified by JD2 output tag)
has been "applied" in the features reporter system. A new table,
"trajectory_structures_steps", keeps track of which step iteration a particular struct_id
represents. Struct_ids can be grouped from the same output by using the existing tag field.
The mover has also a stride option to control how often features are reported.
The mover works in Rosetta Scripts, and could be particular useful as part of a parsed protocol
that is called multiple times, as in the generic monte carlo mover.
In the process of creating this class, I refactored some of the other database and features code,
but behavior should be unchanged.
I also removed SZ_MAX from core/types.hh, as it was causing an unused variable
warning/error on my system, preventing compilation.
This commit merges branch kylebarlow/general_dev into master
Expected test changes:
features: test now uses new reporter
features_database_schema: new mapping table
ligand_dock_script: numerical instability