Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time interval Return / Volatility #4208

Open
RudyNL opened this issue Aug 28, 2024 · 0 comments
Open

Time interval Return / Volatility #4208

RudyNL opened this issue Aug 28, 2024 · 0 comments
Labels

Comments

@RudyNL
Copy link

RudyNL commented Aug 28, 2024

I just started to use Portfolio Performance and stored my portfolio which is only covering a few days.
If I am opening Reports => Performance => Return / Volatility the graph seems to be based on the time interval of my portfolio; e.g. a few days. Changing the the time interval to 1 year, 3 years or longer doesn't change the graph.
If I start a dummy second portfolio with only one equity which I own for 10 years the behavior of Reports => Performance => Return / Volatility changes. Now the graph changes depending on the time interval of 1 year, 3 years or longer.

The expected behavior:

  • The analysis of a portfolio Reports => Performance => Return / Volatility is expected to be independent of any other additional portfolio
  • Return / Volatility analyses are mainly used for investment decisions. So referring to old data before the start of the own portfolio should be possible. That means that you can select the time interval 1 year, 3 years or longer.
  • The current behavior (without the dummy portfolio) should be reserved for the interval "H" = holding period of the portfolio
  • It is understood that the "Entire Portfolio" has a special position because it can only be analyzed for the time interval which corresponds with its existence. So it should only be presented if the selected time interval is shorter then the existence of the portfolio.

I am using Linux with flatpack Portfolio Performance 0.70.4

@RudyNL RudyNL added the bug label Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant