Autoscaling of merged tracks does not follow the current view of the region

[hoholee]

Hi IGV team,

I was trying to make merged tracks with autoscale (related to #1473) using the following code (I'm using igv-webapp.1.10.8 and I believe it loads the latest igv.js 2.12.6):

                    {
                    "name": "Merged - autoscaled",
                    "type": "merged",
                    "autoscale": true,
		    "height": 50,
                    "tracks": [
                        {
                            "type": "wig",
                            "format": "bigwig",
                            "url": "https://www.encodeproject.org/files/ENCFF000ASJ/@@download/ENCFF000ASJ.bigWig",
                            "color": "red"
                        },
                        {
                            "type": "wig",
                            "format": "bigwig",
                            "url": "https://www.encodeproject.org/files/ENCFF351WPV/@@download/ENCFF351WPV.bigWig",
                            "color": "green"
                        }
                    ]
                },
                    {
                    "name": "track1",
                    "type": "wig",
                    "format": "bigwig",
		    "url": "https://www.encodeproject.org/files/ENCFF000ASJ/@@download/ENCFF000ASJ.bigWig",
		    "color": "red",
		    "height": 50,
                    "autoscale": true,
                    "autoscaleGroup": "group1"
                },
                    {
                    "name": "track2",
                    "type": "wig",
		    "format": "bigwig",
		    "url": "https://www.encodeproject.org/files/ENCFF351WPV/@@download/ENCFF351WPV.bigWig",
		    "color": "green",
		    "height": 50,
                    "autoscaleGroup": "group1"
                }

It seems to be working OK at this locus:

However, when I dragged the view a bit to the left I got this:

The two constitutive tracks autoscaled correctly (since the rightmost highest peaks are now out of view), but the merged tracks did not.

This seems to be something wrong in the merged track type where the y-axis range is not computed based on the values in the browser's current view (but somehow extended further to both sides)? Or am I missing something here?

[jrobinso]

Yes I agree that seems to be a bug. I will look at it asap.

[julianstanley]

Screen.Recording.2022-05-17.at.15.48.24.mov

Just adding an additional demonstration of the same problem on the browser mentioned in #1473 after adding the 'autoscale': true flag, live demo here

[julianstanley]

Yes I agree that seems to be a bug. I will look at it asap.

Any update on this / hints on what's happening here? Happy to try to help if there's anything I can do.

[jrobinso]

This is fixed, available in the main branch, and will be released by the end of the month.

[jrobinso]

Released as 2.13.4