BXASolver run cannot be interrupted in jupyter lab about bxa HOT 3 OPEN

I think if you keep hammering the process with Ctrl-Cs (cell selected, keep it pressed), eventually you hit it where it is within the python/ultranest code execution, not within the xspec C execution, and this can stop the iterating.

from bxa.

It is probably an xspec issue actually, xspec may catch KeyboardInterrupt signals and python/jupyter/... does not know about it. You'd have to look at how xspec registers/overwrites signals.

from bxa.

I guess this issue can be closed. Before raising the issue I looked for 'interrupt' in all issues and couldn't find anything. So, maybe some information in the docs on this particular behaviour would be useful for others.

I have not checked if using BXA with sherpa is ok in this respect, i.e. the process can be stopped in a "normal" way.

from bxa.