Feature #679

Permit non-json stuff in Configuration

Added by Rogers, Chris almost 13 years ago. Updated over 12 years ago.

Target version:
Start date:
18 August 2011
Due date:
% Done:


Estimated time:


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 Tunnell, Christopher almost 13 years ago

This sounds really sketchy to me.... we could have it so it loads default configurations without you having to specify it? This could be done by nice parent classes...


Updated by Rogers, Chris almost 13 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.


Updated by Rogers, Chris over 12 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

Committed in r634


Updated by Rogers, Chris over 12 years ago

  • Target version changed from Future MAUS release to MAUS-v0.0.7

Also available in: Atom PDF