This message was deleted.
# mlforecast
s
This message was deleted.
j
Are you refering to this github solution?
j
Thats the solution I've seen, yeah
j
What's wrong with it?
j
Nothing is wrong with it at all as it does work. It's more a question about the UX as the proposed solution diverges from what is established in the rest of the Nixtla ecosystem, and it's also specific for LightGBM, if that makes sense? Support for a generic weighting function is one of the few gaps in the Nixtla libraries that I have seen supported in other forecasters
j
The hard part of having an argument like that is that you might provide an array with the same size as your input, but if you set dropna=True then you'll have a different number of samples on the fit step, so that'll probably cause a lot of confusion. I'll take a look at your example to see how they handle that