finance

Describe your context
Please provide us your environment, so we can easily reproduce the issue.

• replace the result of pip list | grep dash below

dash                      2.0.0
dash-bootstrap-components 1.0.0

• if frontend related, tell us your Browser, Version and OS

  • OS: [e.g. iOS] Windows
  • Browser [e.g. chrome, safari]: Chrome 96.0x, Edge 96.0x, Firefox

🐛 Bug Description

Under MLP implementation there are several variables that need to be initialized. Such as loss, lr, lr_decay, lr_decay_steps, optimizer. However, it seems that the variables lr_decay andlr_decay_steps are indeed being initialized but are not being used at any point in the code.

Expected Behavior

LEAN provides an example of IndicatorVolatilityModel for documentation.

Actual Behavior

There is no example for this feature.

Potential Solution

Adds an example and/or unit tests.

Checklist

• I have completely filled out this template
• I have confirmed that this issue exists on the current master branch
• I have confirmed that t

This issue is a derivation of #613

Why use vectorbt

• GPU acceleration in preprocessing : Finrl pass much time to preprocess data in Colab for me.
• less code to maintain in FinRL preprocessing, currently many work should be do in FinRL preprocessing code part:
  - Currently, I can count 3 bugs in clean_data, and it isn't still solved. I feel the team don't work much on code base

Reading currencies, alphavantage returns a greeting note ("welcome") and this note raises an error in alphavantage.py line 363.

            elif "Note" in json_response and self.treat_info_as_error:
                raise ValueError(json_response["Note"])

For this reason, alphavantage does not work in home assistant.

Heston model has accurate density approximations for European option prices, which are of interest.

The module implementing this method should live under tf_quant_finance/volatility/heston_approximation.py. It should support both European option puts and calls approximations. Tests should be in heston_approximation_test.py in the same folder.

According to @rspadim, functions in entropy.py could use numpy array instead of strings, as it's better to numba.

Guide on how to implement this is available in the comments in PR #311 .

Ulcer Index

in development version: I am ignoring everget

highest_close = close.rolling(length).max()
downside = scalar * (close - highest_close)
downside /= highest_close
d2 = downside * downside
_ui = d2.rolling(length).sum()
ui = np.sqrt(_ui / length)

In development version, sometime I am getting RuntimeWarning: invalid value encountered in sqrt after searching abo

As an intermediate step towards #1015, and various parts thereof, would it be possible to ignore the syntax for features not currently supported, yet use the parts which are supported in trades?
I'm thinking out loud and wondering what effects this may have.

My end goal here is to be able to read a data file https://gitlab.com/snippets/1856416 without errors. Hledger would be able to parse thi