Pausing scripts to wait for user to execute commands

Question

Jeremy Young 2019-2-7

1
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/443818-pausing-scripts-to-wait-for-user-to-execute-commands

评论： Jeremy Young 2019-2-9

Is there a way to pause a MATLAB script and wait for a user to execute some commands (e.g. brushing in the plot and then in the command window)?

Specifically, I want to select some data using the brush tool from the plot, but I want to select multiple groups and then deal with them later (i.e. with the remainder of my script). Typically, I could just do this in 2 parts, one to get the plot, and then after I brush the data and manipulate it into the right structure, run a secondary script to finish up. However, my issue is that I need to do this for a number of different datasets which I was looping through. Changing the parameters to get to the next dataset manually in addition to selecting the data manually seems too tedious for there not to be a better way.

I'm familiar with

pause

and things such as

x = input('Enter something: ')

But this only pauses the script, rather than suspending it to allow the user to interact with the data freely. I think I can brush data and save as variables during a pause, and if I was always going to brush the same number of variables, then this would be fine, but I will select groups based on how the data looks. And because they will be different sizes, I would then save the data in a cell to manipulate in further parts.

I could see such functionality also being useful later if I want to explore the data in the future. See a plot and then want to do something more to it.

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Walter Roberson 2019-2-8

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/443818-pausing-scripts-to-wait-for-user-to-execute-commands#answer_360069

keyboard() -- but you have to know to dbcont to continue afterwards.

1 个评论
显示 -1更早的评论隐藏 -1更早的评论

Jeremy Young 2019-2-9

Thanks, I had a feeling it had something to do with debugging. I didn't think having to insert a break point everytime would be the best solution, and that there must have existed a programatic way to do so.

请先登录，再进行评论。