[BUG] Error showing GFP data in ACh FIBSEM volume: issues with pixi layer

[acardona]

Attempting to render an LSM volume in the StackViewer shows:

pixi.js-lib.665e050c34ee.js:9 WebGL: INVALID_OPERATION: uniformMatrix3fv: location is not from current program

Online I found this is related to lack of gl.useProgram before calling the function. Has anything changed in the StackViewer recently?

See this error with chromium-browser in the ACh FIBSEM volume, loading the GFP stack into a new viewer.

[acardona]

A possible cause is a 404:

[acardona]

The issue may be that the URL is for "s1" of the N5:

https://neurophyla.mrc-lmb.cam.ac.uk/volumes/lsm/1123_v1_Ach_GFP_20220227/s1/attributes.json

... but in disk, it doesn't exist: only s0 exists.

So why, if the admin pages for the LSM GFP stack says only scale level 0 exists, is pixi requesting the s1?

[clbarnes]

I don't think any of those 404s are related:

• websockets are optional, and are not set up for the lsm instance
• source maps are just the dev tools trying to make the code legible
• CATMAID seems to look for extra scale levels by default, even if they're not defined, and just doesn't load the images - this doesn't prevent my seeing the s0 images

I can't see any recent changes to the stack viewer, but will look into it.

[aschampion]

As a data point: the stack loads fine for me in Firefox 98. Could be a difference in WebGL2 between Chromium and FF (I don't have LMB proxy setup on Chrome to test)?

[clbarnes]

I can view it fine on Chromium, using the external stack mirrors (instance: https://neurophyla.mrc-lmb.cam.ac.uk/catmaid/fibsem/, project: 1123 (ACh), stacks -> *Ach* -> add to viewer -> set max to 1024).

[acardona]

For me, neither internal nor external mirrors show anything other than black at 0-1024 display range.

On Apr 12, 2022, at 3:07 PM, Chris Barnes @.***> wrote:

 I can view it fine on Chromium, using the external stack mirrors (instance: https://neurophyla.mrc-lmb.cam.ac.uk/catmaid/fibsem/, project: 1123 (ACh), stacks -> Ach -> add to viewer -> set max to 1024).

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

[tomka]

@acardona, what Chrome/Chromium or Firefox version do you use? I too can load the external mirror in Chromium without issue (version 99.0.4844.74) and see the data when I set the max to 1024 as @clbarnes said. I do see the s1 related 404 as well, so this can't be the issue.

What GPU do you have in use and do you have the chance to try this on another computer to see if it works there?

[tomka]

Unlikely that this has an effect on the behavior you see, but the MIME type error in the console log can be resolved by adding this to your Nginx configuration (or add it to an already imported types file) as part of the http block:

types {
    application/wasm wasm;
}