You're right. The Split Validation operator doesn't have an output to give you the scored results like Cross Validation has. Most people use Cross Validation so this is seldom a problem.
You can easily work around this by adding a Remember operator in the right part of the Split Validation, connecting the "exa" output of Performance to its input. And a Recall operator outside of the validation in the main process, referring to the same name, and sending the results to the process results. Be careful with the execution order, Recall needs to be executed after Remember but the usual connections don't define an execution order here.
If you use Cross Validation, it takes a bit longer but it tests the modeling process on all examples, so I almost always prefer it to Split Validation.
Newbie
Answers
You're right. The Split Validation operator doesn't have an output to give you the scored results like Cross Validation has. Most people use Cross Validation so this is seldom a problem.
You can easily work around this by adding a Remember operator in the right part of the Split Validation, connecting the "exa" output of Performance to its input. And a Recall operator outside of the validation in the main process, referring to the same name, and sending the results to the process results. Be careful with the execution order, Recall needs to be executed after Remember but the usual connections don't define an execution order here.
If you use Cross Validation, it takes a bit longer but it tests the modeling process on all examples, so I almost always prefer it to Split Validation.
Regards,
Balázs