I've noticed that Serpent will exit with non-zero exit codes for some of the sub-commands even if nothing fails. For example
returns an exit code of 255. For most shells, this is interpreted as "something has failed" and restricts some chained commands. When building complex geometries, I like to call an image viewer right after generating the plots with
Code: Select all
sss2 -plot input && feh input_geom0.png
but since Serpent "failed" in the eyes of the shell, the image is not opened. I have also confirmed this happens for the -comp, -elem, -version, -disperse, and -checkstl commands.
The smaller consequence of this is the above inconveniences. The larger consequence could occur if people are running some of these commands entirely from a script configured to exit at the first failure (set -e), the job will terminate even if nothing has failed.