You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TypeError: Cannot read property 'charAt' of undefined
at SVGCircleElement. (11-es2015.50e2a2f87d650b388ab3.js:39)
...
It's happening on this line of the VariantViewer.js
.attr('cy', function(d) {
return variantViewer.yScale(d.alternativeSequence.charAt(0));
})
It seems most variants have an alternativeSequence set, but some do not. I don't know if something changed in the data model that now allows some Variant objects to not have an alternativeSequence, or something else changed?
Printing things out for myself locally, here's an example from MAPK1 of a variant that passes without error:
We're seeing some errors in Pharos coming from the ProtVista component. For example this one, but it seems to happen on most proteins: https://pharos.ncats.nih.gov/targets/mapk1#sequence
TypeError: Cannot read property 'charAt' of undefined
at SVGCircleElement. (11-es2015.50e2a2f87d650b388ab3.js:39)
...
It's happening on this line of the VariantViewer.js
.attr('cy', function(d) {
return variantViewer.yScale(d.alternativeSequence.charAt(0));
})
It seems most variants have an alternativeSequence set, but some do not. I don't know if something changed in the data model that now allows some Variant objects to not have an alternativeSequence, or something else changed?
Printing things out for myself locally, here's an example from MAPK1 of a variant that passes without error:
and the next one that is missing an alternativeSequence and throws the error:
The text was updated successfully, but these errors were encountered: