You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When first implemented, the ITR tool assumed companies were reporting only combined S1+S2 data. However, as benchmarks and corporate reporting have evolved, this is no longer meaningful.
Related to #162 we know that OECM works consistently across almost all sectors and requires separately-reported S1, S2, and S3 data. In the case of TPI, some sectors require only S1 data, some require S1 and S2 data. Some require S3 data only, S1 and S3 data, or S1, S2, and S3 data.
test_different_benchmarks should be updated with embedded data that can be properly used by the respective benchmarks being used, i.e., separate S1, S2, and S3 data. We can create XFAIL test cases where limited corp data works with one benchmark and not others.
This should be done either on the template-v2 branch or after template-v2 has been merged.
The text was updated successfully, but these errors were encountered:
When first implemented, the ITR tool assumed companies were reporting only combined S1+S2 data. However, as benchmarks and corporate reporting have evolved, this is no longer meaningful.
Related to #162 we know that OECM works consistently across almost all sectors and requires separately-reported S1, S2, and S3 data. In the case of TPI, some sectors require only S1 data, some require S1 and S2 data. Some require S3 data only, S1 and S3 data, or S1, S2, and S3 data.
test_different_benchmarks should be updated with embedded data that can be properly used by the respective benchmarks being used, i.e., separate S1, S2, and S3 data. We can create XFAIL test cases where limited corp data works with one benchmark and not others.
This should be done either on the template-v2 branch or after template-v2 has been merged.
The text was updated successfully, but these errors were encountered: