page formatting fails if a NODATA spectrum is in targetid list

[abrodze]

A targetid that corresponds to a NODATA object will cause the page not to generate properly, even if valid objects are also in the list.

Example: https://inspector.desi.lbl.gov/loa/spectra/39627490624276868,39627711727012702

The first targetid corresponds to a spectrum flagged with NODATA, but the second spectrum has no warnings. The following page works without issue: https://inspector.desi.lbl.gov/loa/spectra/39627711727012702

[sbailey]

Thanks for reporting. I suspect that this is an issue with prospect when the input is entirely masked, not an issue with inspector itself. I'll leave it open here until verified and we have a fix. It might be as simple as a bug in the min/max y-range calculation when all inputs are 0 leading to ymin=ymax=boom.

Note that although the rendering for the initial target is broken, the buttons for stepping through spectra still work and it will render the good spectrum fine. If you step back to the broken spectrum you get something slightly more informative, albeit admittedly not ideal. At least that's how it "works" on Safari.

[abrodze]

It does better on Safari than on Chrome. The spectrum inset is very zoomed and toggling with the setting or trying to step through the spectra and come back does not resolve this:

I will note (for at least this example) that if you switch the order of the targetids both pages generate without issue.