Permit non-json stuff in Configuration
Would be great to be able to do more sophisticated stuff with out configuration files - so for example, use math functions on inputs, use (e.g. xboa) units. At the moment we can't import modules because imported modules can't be converted to json. Need a new function that excludes data that cannot be converted to json from the input (and makes a warning message I guess).
Query: do we only want to allow certain types to do this e.g. class, module, namespace (but explicitly not instances of classes). Saves johnny user from getting confused when his xboa.Hit fails to import...
Implemented the general case in rogers. Needs tests.
Updated by Rogers, Chris over 12 years ago
I was playing with input beams - the use case is, for example, to do any sort of complicated geometry (for example moving input beam before D2) we want to use math module (trig functions). To convert from e.g. energy to momentum, would be nice to import particle mass lookup table from e.g. xboa. This is the sort of stuff I would want to do for user-level analyses.