y-axis coordinates and x-axis coordinates are the same

[koustav-pal]

A potential problem here. When x_coords and y_coords are not the same, y_axis inherits axis labels and values from x_axis. Refer, line 222 - 235 in Brick_vizart_plot_heatmap.

[Kelly-ST-HRI]

Thanks for your efforts to develop this package @koustav-pal

We've replicated this issue (@kuguit and I) when plotting trans-chromosomal contacts between chromosomes of different sizes (x-axes chromosome was smaller than y-axes). The y_coords therefore did not match the axes limits defined by x_coords or the maximum length of the shorter chromosome.

Error in h(simpleError(msg, call)) : error in evaluating the argument 'x' in selecting a method for function 'end': subscript contains out-of-bounds indices

I've found the bug causing this and have a working solution which allows:

• different co-ordinate inputs for each chromosome
• plotting asymmetric matrices which axes of different sizes
• inverting the matrix to (optionally) allow plotting the larger chromosome on the x-axis from the same "brick" file

I've tested this solution by modifying the function code and running "source" on this R script to import the update version. I'll submit a pull request with recommended changes.

[Kelly-ST-HRI]

I think this solution will resolve issue #17 as well.

[Kelly-ST-HRI]

I've added these as 2 separate PRs as #25 directly addresses this issue while #26 significantly changes the codebase to allow transpose matrices in the lower triangle to be plotted.

• different co-ordinate inputs for each chromosome (see PR #25)
• plotting asymmetric matrices which axes of different sizes (see PR #25)
• inverting the matrix to (optionally) allow plotting the larger chromosome on the x-axis from the same "brick" file (see PR #26)