the end goal would be just having to design the feature + transformations and ship it through the testing pipeline until it hits the portfolio.
i already had a defined method for feature construction, but it was very clunky.
also i spent quite a bit of time designing the alternative data part which integrates nicely into the process all the way to the tradable alpha if that makes sense. imagine that you wanna trade some idk weird parking lot data signal on walmart. how do you integrate that data in the pipeline so it doesnt break everything else but can still added to the pool of tradable signals? well that turns out to be a bit more complex than it might appear.
so the first thing is getting at an idea of how strong this feature is. right now, and this is not optimal yet, im looking at IC/IR over multiple periods and avging them out.
i think this is fine for momo/trend stuff, but for other stuff i cant just avg IC together because features give us different lengths of information depending on what they are targeting right ? i cant be avg a short-term alpha in 60 days when the feature is design to capture short term reversal or carry. so theres nuances ill get into later.
also there's other stuff it picks up that we want to neutralize for, and that will be another part of the work.
my portfolio still allocates based on feature ranking rather than a forecast over a time horizon if that makes sense. I am not looking each day at what features has the highest EV tomorrow, but rather which features rank highest that day. it should be pretty close to the same thing, but isn't, again especially when new different features hit the portfolio.
View Tweet


