Hi ShallowGoldfish8 ,
I'm not sure I understand the scenario. Can you please elaborate? In the end the model object is there so you can easily fetch the raw data and track it.
I see. When you're working with catboost, as what type of object is it being passed?
Steps (pipeline components):
Load the model Infereces witht he model
Its equivalent tomodel = Step1(*args) preds = Step2(model, *args)
After step 1, I have the model loaded as a torch object, as expected. When this object is passed to step 2, inside of step 2, it is read as an object of class 'pathlib2.PosixPath'.
I assume that is because there is some kind of problem in the pickling/loading/dumping of the inputs from a step to another in the pipeline. Is it some kind of known issue or is there anything I am doing wrong? When doing the same for a catboost model it works perfectly