Alejandro de la Vega

No problem. By the way, if the API becomes a barrier we can very easily modify it. For example, if it really is hard to do resampling in JS and...

Hey @jsmentch. That's awesome. Does that mean there's no need for issues: #828 and #829? I just had a quick look at it and it looks like a pretty big...

Oh, I should also mention that I have the following issue open: #881 The idea is to allow the querying of stimuli from the API. This could possible be integrated...

1) We need to have the task selector by a checkbox versus radio selector 2) Changes need to be made to the backend to allow this. Most of the report...

3) Need to check if I extract the same Predictor in all tests, is the Predictor id separate for all tasks? I think so and this might make it difficult...

Yeah, that would work. I mean that's already available because you can query `/api/predictors` and request all, rather than only the latest. Then it would be up to the front...

I think given the changes to `fill` this is just a matter of either updating the analysis using `/fill` or ensuring to request the correct predictors on `/api/predictors` when showing...

It's okay I'll leave it open because it means we should do more testing for small screens (common use case)

Haha, I also don't read documentation on purpose ;) I think adding a permalink to each one would help

Looking into it. Do you have any privacy extensions active per chance?