This module allows you to analyze existing cross correlation between HitBTC NEM USD and Yobit Waves USD. You can compare the effects of market volatilities on HitBTC NEM and Yobit Waves and check how they will diversify away market risk if combined in the same portfolio for a given time horizon. You can also utilize pair trading strategies of matching a long position in HitBTC NEM with a short position of Yobit Waves. See also your portfolio center. Please also check ongoing floating volatility patterns of HitBTC NEM and Yobit Waves.
Assuming 30 trading days horizon, HitBTC NEM USD is expected to generate 1.4 times more return on investment than Yobit Waves. However, HitBTC NEM is 1.4 times more volatile than Yobit Waves USD. It trades about -0.04 of its potential returns per unit of risk. Yobit Waves USD is currently generating about -0.13 per unit of risk. If you would invest 51.82 in HitBTC NEM USD on March 20, 2018 and sell it today you would lose (13.48) from holding HitBTC NEM USD or give up 26.01% of portfolio value over 30 days.
Pair Corralation between HitBTC NEM and Yobit Waves
Overlapping area represents the amount of risk that can be diversified away by holding HitBTC NEM USD and Yobit Waves USD in the same portfolio assuming nothing else is changed. The correlation between historical prices or returns on Yobit Waves USD and HitBTC NEM is a relative statistical measure of the degree to which these equity instruments tend to move together. The correlation coefficient measures the extent to which returns on HitBTC NEM USD are associated (or correlated) with Yobit Waves. Values of the correlation coefficient range from -1 to +1, where. The correlation of zero (0) is possible when the price movement of Yobit Waves USD has no effect on the direction of HitBTC NEM i.e. HitBTC NEM and Yobit Waves go up and down completely randomly.
Build portfolios using Macroaxis predefined set of investing ideas. Many of Macroaxis investing ideas can easily outperform a given market. Ideas can also be optimized per your risk profile before portfolio origination is invoked.