percentile | Calculate percentile response times from logs | Analytics library

We convert to a logical vector (.x < quantile(.x, 0.30)) and get the count with sum - as TRUE -> 1 and FALSE -> 0

Use numpy.typing.ArrayLike:

You can do something like this, if I understand what you want

(First, a quick explanation of the pivot_longer() options that I use)

• cols selects the columns you want to pivot
• names_to with multiple elements allows us to pivot into multiple columns
• names_prefix allows us to remove a common prefix across the columns that we want to pivot
• name_sep allows us to indicate how the multiple names in names_to are broken up in the original columns

you can leverage the parameter raw=True in the apply to pass a numpy array instead of Series. You need to slightly change your function to work with an array.

This may be what you want

If the imgur you posted is truely your dataframe, then the problem is that you are performing qcut on a single-rowed dataframe. How can you split up a single row into 100 quantiles? Pandas is trying to create a bunch of bins of different quantile values, but since you only have one observation, all of those bins start and end in the same place. I can prove this is the case by recreating your error using a single row df:

A couple of things to consider:

• While it's definitely desirable to quickly evaluate the performance of many combination models, it's pretty impractical. The best option would be to evaluate your models individually, and then create a more simple combination using, e.g. the 2 or 3 best ones
• As an example, consider that you can actually have weighted combinations - e.g. 0.75 * ets + 0.25 * arima. The possibilities are now literally endless, so you start to see the limitations of the brute-force method (N.B. I don't think fable actually supports these kind of combinations yet though).

That, said, here's one approach you could use to generate all the possible combinations. Note that this might take a prohibitively long time to run - but should give you what you're after.

We may use findInterval

I can't check PowerShell 3.0 for you. But the following works in Windows PowerShell 5.1. I've got two solutions, one which includes the first info line as part of the match and one that does not.