Model block configuration options should be in docstrings

[lucianopaz]

At the moment, all the user facing methods have a common signature method_name(self, *, data=None, config=None). To find out the config options, the users should go to the source code, find which methods are called and then infer the config keys and values from the called methods signature or docstrings. To make the user's life easier, we need to document this information in the user facing method_name itself. Our Model object could then dynamically read in the passed in blocks to set an appropriate docstring with all of the possible configuration keys and options.

• Document initial config options Add docstrings for the initial config options of Model blocks #174
• Document summary config options
• Document plots config options

Related to #36

[ricardoV94]

I am not sure what we can do in terms of dynamic docstrings. Last time I looked at it Python seemed pretty limited

[ricardoV94]

I think the most reasonable solution will be to add docstrings to the blocks, and tell users to check them with help or ? in jupyter.

[lucianopaz]

Yeah, let’s do that