Change Point Detection

Change point detection is un supervised learning, so you have to define your own metric of how you're going to be satisfied with your solution. Would you encourage people to do some sort of smoke testing? You know, if i'm the manager and i've tasked the team to implement some sort of change point detection, i could put in the extra effort and find a way to inject a change point just to test the methods. Is it worth doing? Definitely, definitely in favor of that.