Error in Market Cap Allocation Graphics

Marco,
I noticed when backtesting to a previous date, and current holdings has stocks which have seized to trade, then the graphic of Market Cap Allocation displays some allocation as “MicroCap”, when in fact all stocks where either large or mid-caps. This is wrong and confusing when one checks historic allocations. I noticed this when selecting stocks from the Prussell 1000 universe, which has no micro-caps.

Georg

Marco, I think this needs to be fixed.
I just checked a S&P model which has no micro-caps. Whenever the historic current holdings show stocks that have seized to trade, then the allocation picture indicates that current holdings has micro-caps.

Georg.

Marco,
I see that you want to extend P123 to Canadian and European stocks. Before you do this you should fix the current mistakes, which are patently obvious. I don’t understand why nobody from P123 reacts to my post. Nobody seems to care.
Georg

The MktCap charts get their data from the “current date” data server at the moment, they do not use the sim end date. I guess not many use it in the context of a sim. Should be an easy fix. Thanks

Thanks Marco for looking into this discrepancy. I use that graphic to check market-cap allocation for historic dates to compare with Buy Daily Average (bottom 20%) figure to see whether BDA makes sense.

Georg.

Marco,
I note that this graphic display of current holdings still shows for historic dates the stocks which are no longer listed now as micro-caps. Perhaps you should remove this figure if you don’t want to fix the error, it is a bit misleading
Georg

P123 guys. Why don’t you fix this or remove the incorrect historic market-cap allocation graphics?

Marco, as you said almost 2 years ago: “this should be an easy fix”. So perhaps a programmer can get to this asap.
Thanks,
Georg

I would also like to see this fixed

I have this happened many times. Although we can just replace micro-cap with large cap, it would be really great if it can be fixed.

Actually this has been fixed a few months ago.