I am struggling with an odd issue with Miner.   The context - I am creating 3 sets of data within my project - a training, validation and test set. So far, so simple. The issue has come in where I want the test set to be a purely out-of-time set (the few months after the development period), while the validation and training set are just a 30/70 split of the remaining, in-time data.   What I have done: I have placed SAS Code nodes after the raw dataset, which split the data into and in-and out-of-time set. This way the in time set can be partitioned as usual using the Data Partition node. In the code I specify that the out of time is the test set (using the macro variable for the test export set). The problem is that Miner insists on creating passing through the original training set too.   This is causing issues when I feed this node into the modelling steps after I split the validation set, as there are now 2 training sets. I can't figure out how to make Miner drop the one or at least allow me to select one. The crude solution I have at the moment is to be sure that the correct training set is "on top" when the process is laid out, but this is not a permanent fix as once the model is handed off just rearranging the physical position of the nodes will break the process.   Am I missing something obvious or is there no way to prevent a SAS Code node from exporting a training set? ... View more