Please rerun the job and you should find the plots will be generated now
Ted
p.s. For the curious, all our modules run containerized (either singularity or docker) and on several different compute environments (AWS and academic supercomputer centers). The supercomputer center where GISTIC jobs run (who shall remain nameless) just changed their location for temporary files ($TMPDIR) without notifying users. Non-containerized apps continued to work fine, but containerized applications like our modules needed to change the volume bindings for any module that used temporary files, such as GISTIC does when generating plots. If temp files were not created, things continued to run normally