-
Notifications
You must be signed in to change notification settings - Fork 71
Conversation
This is @FrederickFa's suggested (quick but not ideal) change to address the problem discussed in #499. This is also discussed in ADO#661, where there seems to be still some debate on the proper long term solution.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Also, we actually just go back to an earlier version of PACTA (7e125aa) but filter holdings of zero portfolio weight too and also repeat this process for CBs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
thanks @FrederickFa and @jdhoffa... I think we need to wait for @AlexAxthelm's approval on this one though |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll admit that I'm out of my depth on the methodological impact of this change, but conceptually, it makes sense.
putting back into draft until a final decision is made in ADO-661 |
@cjyetman who else needs to be consulted regarding this decision? |
@jdhoffa according to the ADO thread, I suppose Maarten and Nayra |
I believe Maarten's feedback was as follows: |
also hi! hope you guys had nice holidays hahaha |
I also understood it that way. But since they are currently still integrated into the analysis, we should filter them out with the simple solution proposed here. |
That's not what this PR does. It does not prevent uploading negative ISINs, and it does not flag them as invalid in the audit file. The filter in this PR occurs long after the audit file is created. |
That makes sense, but we don't need further input from Maarten or Nayra do we? We need to filter out these positions somewhere in |
That's what I did before and @FrederickFa said it was wrong... #499 |
Aw barnacles, ok... |
Yes you are right this is not exactly what this PR does. It does make sure they are not part of the analysis and also maybe that these positions are not included when calculating exposures (I am not sure at what step this happens). It does not make sure they are not uploaded or filtered right away. In terms of flagging, this is already happening, which is why it is so confusing. We already add flags that these are not valid input values (lines 666 & 705) but do include them in the analysis later on.
Well, there is no right or wrong, but I think the aspects mentioned in #499 are still relevant. Since we do not yet have a methodological position, I think it is better to intervene as little as possible in the portfolios, which for me means not analysing short positions for the time being but leaving everything else untouched. Argument in #499:
If the general consensus is to filter them out of the portfolio immediately, that is also a valid solution. We should just make sure that we move forward with one solution or the other and not leave it as it is. |
I was just thinking and maybe we should go even further and have a filter like this:
instead of:
For example, if a user would upload a portfolio which holdings have negative values in |
This seems stale, and also in a deprecated repo. Ok to Close? |
actually, I think we never came to an agreement on how to deal with this.... probably should still consider it |
Maybe then we:
|
Just trying to do some house-keeping |
💯 agree with that |
I can't close this PR because I dont have admin to this repo anymore, but the rest is done. |
closing but tracking issue here https://github.com/RMI-PACTA/pacta.portfolio.analysis/issues/177 |
related to ADO-661
supersedes #499
This is @FrederickFa's suggested (quick but not ideal) change to address the problem discussed in #499. This is also discussed in ADO#661, where there seems to be still some debate on the proper long term solution.
This only changes the so-called "offline" version, which may be only used by MFM anymore, though we can't really know that for sure.This will also impact what runs on transitionmonitor