Misc Resources

Updated on Nov 25  2017

Interesting Articles
Mocap Reading
Renderfarm Tips
Houdini / Renderfarm

Linux Quick Guide


Quick Links to Conferences:
Siggraph archive
Siggraph University

Quick Links to Websites:

copyright  Deborah R. Fowler
Linux Quick Guide

Deborah R. Fowler

Linux Quick Guide

Updated on April 22   2016

Linux Quick Guide
to most commonly used commands
lists the contents of the directory (folders are blue, files are black font)
MS-Dos uses dir - on a whim, I tried this on linux and it works too!
change directory ie. cd ../  will go up a level
or you may want to do to your home directory cd ~  or cd
home directory
copy and if it is an entire directory, cp -r
present working directory (where you are)
current directory
current directory
processor status (ie. what jobs are running)
kill -9 jobid
kill the job with this id from ps no matter what
kill -segv will force it to save a version to /tmp
make a directory (new folder)
cd /opt
installations of Houdini can be found here
run an application as a background process
gedit &
this will leave the terminal window free to use
keyboard up arrow
recalls the last command to save typing or ...
history lists recent commands and you can type !# where # is the number  from the list

and less common but useful commands
prints your paths and environment settings
pipes a file to terminal display

There are so many things you can do in linux from the command line!
You can create a .custom_bash script to be run when you log in.
I would strongly advise you to use at least one line in there:
alias rm='rm -i'
That way it will query you when you delete a file.

Type in alias -h to see more options.

To run a script on our system, type ./name in a terminal, or double click on it in Nautilus (beware you must actually be in the directory or it will fail)

About.com has some useful linux summaries, particular here is a comparison of DOS versus linux commands.

Houdini Command Line rendering

This command can be used to render locally. It is a command line tool (it actually is a shell script that lives in $HFS/bin which you can take a look - use gedit, or more - more views the file without editing - very handy!)

For example:
hrender -d mantra1 testSphere.hipnc

This assumes mantra1 is an output rop in the hip file.

hrender -e -f 1 3 -v -d mantra1 testSphere.hipnc

-e -f 1 3 instructs it to render frames 1 through 3
-v verbose
-d output driver

Type in hrender to see all the options (for example -o test.'$F4'.exr  added to the line above would write the information to the files if you have not specified them in your mantra node.)

Troubleshooting on the farm - render locally with command line as a first step to debugging the problem by copying the command from the log file and running it in a terminal window (with renderfarm references removed).
ie. in the log file you will see:
/tmp/hrender -e -v -R -f 250 -o /tmp/farm/Job_285332/blahblah.$F4.exr -d mantraTest blahblah.hipnc
hrender -e -v -R -f 250 -o blahblah.exr -d mantraTest blahblah.hipnc
hrender -e -v -R -f 250 -o blahblah.'$F4'.exr -d mantraTest blahblah.hipnc

For caching
hscript file.hip
cd /out
render -vA (verbose, alfred) -I (that is an I as in interleave) nodetoprocess ... so for example it looks like
render -vA -I merge1

You can do the same thing in window from the Houdini Command Line Tool window (it's a cmd window with the proper paths/environment set) (It is in the All Programs/Side Effects Software /Version/Utilities/Command Line Tools)