feature request: interactive glassbox prescription design

[mh105]

Per our discussions in feature request: glassbox prescription function #1, we would like to add a full interactive prescription design mode for the glassbox() call.

The desired behaviors are:

• glassbox() will be called without parameter arguments other than eye that tells it where to load the data.
• Then via prompting, glassbox() will step through all the possible pipeline functions one by one.
• For each pipeline function, the prompt message should give a -h style introduction of all the possible parameters for each function as well as some guidelines on how to specify each parameter.
• The prompt should then be able to accept multiple key-value pairs for the parameters, or an empty cell like [] or something like that to use default value, as well as a special command like "Skip" to skip the pipeline function entirely.
• "Undo" should also be a valid input here, which will revert to the n-1 pipeline function and ask about parameter inputs to this previous function. -> this is what will allow users to undo multiple steps in glassbox().
• glassbox() will then run the pipeline function, spit out a diagnostic plot.
• The prompt screen then gives the user the options (if they didn't choose to Skip) to Continue, Abort, or Undo.
• Choosing Continue will advance to the next possible pipeline function.
• Choosing Abort will quit the glassbox() function and return the time traces up to the point (including the last pipeline function) when the user chose to Abort.
• Choosing Undo will undo the processing done by the pipeline function and revert to the prompt that asks for parameter inputs. This way the user gets the opportunity to interactively try out different parameter values and proceed to the next step once they feel satisfied.
• glassbox() or the eyeris object should also have a dictionary to hold the detailed parameters used for each pipeline function done to the data, in addition to a string that indicates that a certain function is applied. In other words, if the user did deblink, the bleeding duration used at the beginning and/or the end of a blink period should be saved and can be easily queried after glassbox() completes.

This is a goal for the next release after beta, but it will be a very useful feature for broader adoption of this preprocessing package.