OK, the problem with running this from /media/disk is that the executable is available only to the frontend, but not the compute nodes. Doing it from /home/user solves the problem, because that directory is NFS exported.
For your work, I don't see any reason why PelicanHPC shouldn't work well. You will definitely want to mount external storage (during the initial boot up, replace "ram1" with something like "sda1", where that is the device name of a partition formatted as ext2 or ext3. For speeding up the work, I have a couple of ideas. If it is possible to generate all the information needed to plot a frame ahead of time, do that, and then plot complete frames on nodes. If you absolutely need to have the .bmp file (and not just the input parameters) before the information needed to plot the next frame can be computed, then slice the frames into blocks, and compute blocks on nodes. This might be complicated if the pixels on either size of a slice are not independent. That's the reason I would try to do the first approach.
Plotting and video rendering is pretty widespread, but I don't know much about it. You might try searching for some topic-specific mail lists to get advice.
Cheers, M.