[ENH] n_jobs/_n_jobs, parameter in classifiers

[TonyBagnall]

the use of n_jobs/_n_jobs in CollectionEstimators is confusing and could be tidied up.

See https://github.com/aeon-toolkit/aeon/blob/main/aeon/base/_base_collection.py#L92 where _n_jobs is defined. This is not really enforced in any way currently.

[baraline]

May be related to #1797

[lucifer4073]

Hi, is this issue resolved ?

[MatthewMiddlehurst]

No i don't think so.

[lucifer4073]

the use of n_jobs/_n_jobs in CollectionEstimators is confusing and could be tidied up.

See https://github.com/aeon-toolkit/aeon/blob/main/aeon/base/_base_collection.py#L92 where _n_jobs is defined. This is not really enforced in any way currently.

Interest to work with this one. I plan to clarify the usage of _n_jobs which will be overwritten by n_jobs if defined in child class. Also instead of raising Attribute error we can run a single thread.