Currently the data is written to disk right at the end of the template, and this means that this data is often not captured properly, so we may need some intermediate chunks of code to do this earlier in the workflow.
It is likely we may create multiple outputs that also uses the additional columns created by the outlier detection piece.
Currently the data is written to disk right at the end of the template, and this means that this data is often not captured properly, so we may need some intermediate chunks of code to do this earlier in the workflow.
It is likely we may create multiple outputs that also uses the additional columns created by the outlier detection piece.