Thanks for your reply. I'll incorprate the stoperror('all'); ... somewhere.
The iterative "for loop" resides in a worksheet.
It calls Property() from the thermophysical,coolprop package.
The crash is an error ->
"Error, (in ThermophysicalData:-CoolProp:-PropsSI) Two-phase inputs not supported for pseudo-pure for now : PropsSI("Z","P",1289238.529,"T",112.1727954,"Air")"
From this error it looks like I've hit the saturated vapor line for the iteration at 112.17K. This would look correct on a T-s plot for the isentropic process.
I might have the answer through a different way to do debugging without single stepping up to the error, but do find it frustrating to not be able to stop say 5 iterations before the break-out and then single step through to follow what's happening in code vs. physlcs world.
The value returned from the error "1289238.529" is suspect and I don't recogize this. The PropsSI call is a subfunction of Property and this call is getting Z, compressibility, but I did not ask for this that I am aware of, so is has to be sub-process. I did achieve 412 iterations with what looks like physically resonable answers until it "error'ed" out.
I would presume the thermophysical package "property" method/procs are locked would not let single stepping into them, and so would:
"Stoperror('all'); allow to watch the process up to the error?
Any assistance with debugging techniques into Maplesoft packages from a worksheet level call (within "for loop") and tracing the variable through until the error would be very helpful.