Open seabbs opened 4 years ago
It looks like this is caused by the tbats
model. For me setting all its parallel arguments to FALSE
failed so dropping for now. This is not optimal so a workaround or internal protections for users would be preferred.
When using
forecastHybrid
more than one core is used despite parallelization being turned off explicitly. This means that large runs are slow as cores conflict. Identifying someway to internally turn this off or externally prevent more than one core being accessed would both be good solutions.This could very easily just be user error rather than a bug!
Issue opened on the package repo (https://github.com/ellisp/forecastHybrid/issues/92)