Is your feature request related to a problem? Please describe.
exp.inferParameters could be adapted to functions as the NewExpFactory in MControl. In other words inferParameters could infer the parameters of any custom experiment, not just Signals ones.
Describe the solution you'd like
inferParameters should check the class of the file called. If just a function it should assume it's an expDef. It should then try to call a basic params file or prompt the user for one (the user could also provide a set of previous params)
For signals expDefs, it should call a new function that does what inferParameters currently does, e.g. exp.signalsParams, to find params from the expDef. It could add on SignalsExp parameters such as screen background color and exp panel function. These are then used along the way (e.g. services, configureSignalsExp, ExpPanel.live). These extra params can be hidden from SignalsExp using a setdiff calling signalsExpParameters with no args.
Is your feature request related to a problem? Please describe. exp.inferParameters could be adapted to functions as the NewExpFactory in MControl. In other words inferParameters could infer the parameters of any custom experiment, not just Signals ones.
Describe the solution you'd like
exp.signalsParams, to find params from the expDef. It could add on SignalsExp parameters such as screen background color and exp panel function. These are then used along the way (e.g. services, configureSignalsExp, ExpPanel.live). These extra params can be hidden from SignalsExp using a setdiff calling signalsExpParameters with no args.