Joshua Taillon

Responding to this comment from #5182: > The problem is that different extra fields need different range options, e.g., date vs number vs text, and hence, when a user selects...

Ok, thanks for the context. Feel free to leave this open as a feature request, or close it if you wish. It would be nice if it worked the way...

When generating documentation, it also shows an incorrect range (although it matches the JSON schema in some ways):  In this example, the range should just be `MixinOne or MixinTwo...

I just came across this issue as well, and it was a surprise to not see the `sharelink` field in the bulk `experiments` response. For our use case, it would...

This is something I have noticed as well. It occurs only when using the Qt4 backend. I did some initial testing in this issue (https://github.com/hyperspy/hyperspy/issues/561). The eventual resolution of that...

I just noticed this issue again today...

It seems as though if you change the fitting method to Gaussian, it doesn't crash (like @magnunor said), but then also if you switch back to Power Law, it still...

Actually, now that I test it more, I don't think it's the case. It's so strange that sometimes it crashes right away, and then other times takes a lot of...

I think the issue is in `powerlaw.estimate_parameters()`. Trying to hunt it down now Update: Looks like it might be in the `integrate1D` calls in that method

@francisco-dlp So I couldn't find the exact reason for failure, but I believe I've isolated it to the integration done in the [two-area method](https://github.com/hyperspy/hyperspy/blob/RELEASE_next_minor/hyperspy/_components/power_law.py#L123-L124). I tried to change the estimating...