evalml icon indicating copy to clipboard operation
evalml copied to clipboard

Future-proof the location of unsupported decomposer frequencies

Open eccabay opened this issue 2 years ago • 0 comments

we might want to move [unsupported decomposer frequencies] either 1.) into the stl_decomposer module and/or 2.) make it returnable by the decomposer itself. Then we can dynamically know what decomposers support or do not. You could also build the parametrization list and parametrize across STL decomposers in your decomposer test that way.

Part of the motivation behind the move, in my mind, is the answer to "where should I go to find what frequencies are not supported by X Decomposer?"

Originally posted by @chukarsten in https://github.com/alteryx/evalml/pull/3794#discussion_r1008425041

eccabay avatar Oct 28 '22 20:10 eccabay