Hello Satyapravin,
I'll take a crack at reading and digesting the paper you referenced. Do you have access to the Q research platform yet? My understanding is that you can simply submit any ol' algo to the contest, and "Presto!" you get access. Or you can request access and be put in a queue.
Regarding developing a trading strategy, the integration of the research platform and the backtester/trading API is almost non-existent, so I don't see a path to set up any kind of online/automated approach (e.g. where daily you would automatically identify new baskets of securities and feed them to the trading API overnight). However, manually, you can download entire notebooks in various formats (IPython, Python, & HTML). So, if you performed analysis, you could download it, and then massage it into a format compatible with fetcher. So, the idea would be to run a periodic screening analysis in the research platform, to find your security baskets, and then get them into the trading platform via fetcher for backtesting and trading (or you could copy and paste, but that would require stopping the algo, if it is running live).
One open question is whether the research platform, in its current manifestation, could be used for screening. I think that if one is careful not to create a memory leak, it could work (I was able to loop over all ~ 20,000 securities in the database, computing some simple summary statistics of each, overwriting the memory as each new security was loaded).
If I understand correctly, the basic approach here is to synthesize a trading pair, by creating two security baskets. So, it is a matter of picking the number of securities in each basket, N and M, the securities, and their weights. It might be worth a head scratch to sort out the overall difficulty of the computing problem, particularly as N and M become large. Presently, the research platform has no parallel computing capability. In theory, one can run multiple notebooks in parallel (each launched manually), but the RAM is shared in some fashion (you can't actually see what's going on under the hood, in terms of utilization of available computing resources). To pair down the problem a bit, it is possible to pluck out a subset of securities from the data base. For example, say you wanted to look at only ETFs for you baskets. It is a matter of pasting in a list of the ETF symbols, and the analyzing only those securities in the Q database.
Grant