Refactoring econometrics for SDK usability

[jmaslek]

The econometrics menu is nice, but the SDK usage is not friendly because how we do it in the terminal. This menu needs some refactoring so that the SDK is usable. Still love you @JerBouma.

Things done:

• Refactor OLS so that the SDK can take in dataframes instead of a dictionary of dataframes: This will do fixes [Bug] SDK - openbb.econometrics.ols displays more objects than feasible #3368 fixes [Bug] SDK - openbb.econometrics.ols requires dictionary datasets instead of DataFrames #3367 fixes [IMPROVE] SDK - openbb.econometrics.ols input can be much nicer #3369
  

• Fixes [Bug] SDK - openbb.econometrics.norm should produce a chart #3366 by making chart=True by default
  

• Fixes [Bug] SDK - openbb.econometrics.coint is messy and you can't plot anything #3373 by refactoring the coint function to return a df only. I also changed it to allow a variable number of inputs in the sdk and allowing for the plot to show up when doing chart=True

• Fixes [Bug] SDK - openbb.econometrics.granger returns a messy output #3370 and fixes [Bug] SDK - openbb.econometrics.granger - Error: get_granger_causality() missing 1 required positional argument: 'lags' #3323 for the granger SDK function
  

• Refactor dwat function to take in an OLS model instead of the residuals. I think this cleans up. Made a note about the view in the model docstring

    Returns
    -------
    float
        Test statistic of the Durbin Watson test.

    Notes
    ------
    When using chart = True, the dependent variable in the regression must be passed to view the residuals

• Complete the fixes [Bug] SDK - openbb.econometrics.dwat, openbb.econometrics.bgod and openbb.econometrics.bpag can't be used #3372 -- sdk functions now input models
  

• Refactor panel. Fixes [Bug] SDK - openbb.econometrics.panel shows the same thing twice #3374

[jmaslek]

There are a couple functions that need some cleaning up for the sdk, but if anyone wants to review this overnight feel free :)

[JerBouma]

The econometrics menu is nice, bla bla bla love you @JerBouma.

Thank you <3

[jmaslek]

I just have panel left

[JerBouma]

Make sure by the way that if you do chart=True (or anything else) that it doesn't print the richt table. Those should always be DataFrames.

[jmaslek]

Make sure by the way that if you do chart=True (or anything else) that it doesn't print the richt table. Those should always be DataFrames.

Ummm that's the desired behavior to print the nice charts when chart = True. Doing otherwise would be a whole refactor.

[JerBouma]

Make sure by the way that if you do chart=True (or anything else) that it doesn't print the richt table. Those should always be DataFrames.

Ummm that's the desired behavior to print the nice charts when chart = True. Doing otherwise would be a whole refactor.

Just making sure we don't mean different things, I mean that if you use chart=True I don't want to see the table too, see:

Whereas this screenshot also shows the Rich table. That looks wrong.

[jmaslek]

Just making sure we don't mean different things, I mean that if you use chart=True I don't want to see the table too, see:

Not possible with the current architecture.

[JerBouma]

Ok ok

[DidierRLopes]

Ideally we would have the raw=True when we want to output the table. Is this not possible? @jmaslek @JerBouma

Spitting both is very suboptimal, imo. Would be better to just spit the chart than both

[JerBouma]

Ideally we would have the raw=True when we want to output the table. Is this not possible? @jmaslek @JerBouma

Spitting both is very suboptimal, imo. Would be better to just spit the chart than both

The rich table shouldn't be an option in the first place, you can rely on the default output (without chart=True) which is a DataFrame object. But if this requires too big of an architectural change it isn't too big of a deal for now.

[jmaslek]

Ideally we would have the raw=True when we want to output the table. Is this not possible? @jmaslek @JerBouma

Spitting both is very suboptimal, imo. Would be better to just spit the chart than both

I think this gets into the question of the default output. In this menu its primarily tables so we want raw=True by default. You can actually pass plot=False in these cases. So I think its a matter of what the default output is

[jmaslek]

The rich table shouldn't be an option in the first place, you can rely on the default output (without chart=True) which is a DataFrame object. But if this requires too big of an architectural change it isn't too big of a deal for now.

If you are in a script, you wouldnt get the default output and could instead see a table with view. So if you want the default output, dont use the _view.