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
Technically not directly lsqfitgui related, but it would be neat to have a wrapper for plot_gvar taking DataFrames as inputs like px.lines. Maybe, instead of having different rows and columns, also having a select widget for different groups.
The text was updated successfully, but these errors were encountered:
with a inherited GVarScatter which pre-processes the y to a y mean and y error.
Looking at the current go.Scatter, this needs to overload the setter of y.
Since, on __init__(...), y is stored directly in self["y"] (not using the setter), one also needs to adjust the __init__.
This works just fine when creating figures. However, it fails for the express version. My prime suspicion is that, at some point, the dict is manipulated and I am not catching it; but I am unsure here.
I suspect a better route would be manipulating the input data frame to avoid messing around with the hidden Plotly infrastructure; and thus reduce the chance that the intended feature needs updating.
Technically not directly
lsqfitgui
related, but it would be neat to have a wrapper forplot_gvar
takingDataFrame
s as inputs likepx.lines
. Maybe, instead of having different rows and columns, also having a select widget for different groups.The text was updated successfully, but these errors were encountered: