You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following example which intentionally involves a bug related to a missing direction parameter in the FluxRegion object causes a Jupyter notebook kernel failure with the message: The kernel appears to have died. It will restart automatically..
For MPI jobs, I think we may need to continue calling MPI_Abort to make sure that all the processes stop working on an error. But for single-process functions I think it may be as simple as changing the meep::abort function to throw an exception, and adding an %except handler in SWIG to make sure this is caught as a Python exception.
The following example which intentionally involves a bug related to a missing
direction
parameter in theFluxRegion
object causes a Jupyter notebook kernel failure with the message:The kernel appears to have died. It will restart automatically.
.The error message from Meep which describes the cause does not appear in the notebook but rather in the terminal which launched the notebook:
It would be useful, for debugging purposes, etc., to have all error messages appear directly within the notebook.
The text was updated successfully, but these errors were encountered: