Programming Page

1. C++
2. TCL
3. Shaders
4. Slim Templates
5. Slim Script
6. MEL
7. Perl
8. Python
9. tcsh
10. Linux
11. Subversion

if ( $decimal_places < 1 ) {     return $value; } float $dp = pow( 10.0, abs($decimal_places) ); return trunc($value) + (trunc($dp * ($value - trunc($value))) / $dp);

}

// Select the object with the animation keys on its translate X,Y,Z then 
// call this script with the frame range you want the curve for, e.g.
// de_makeCurveOnTranslateKeys(10, 256);

global proc string de_makeCurveOnTranslateKeys(int $start, int $end)
{
	string $sel[] = `ls -sl`;
	string $cmd = "curve -d 3 ";
	string $k = " -k 0 ";
	int $i = -2;
	int $j=$start;
	for ( $j=$start; $j<($end+1); $j+=1 )
	{
		float $pos[] = `keyframe -at t -t $j -q -eval $sel[0]`;
		$cmd += ( "-p "+$pos[0]+" "+$pos[1]+" "+$pos[2]+" " );
		if( $i > ($end-$start-3) )
		{
			$k += (" -k "+$i);
		}
		else
		{
			$i+=1;
			if( $i < 1 )
				$k += (" -k 0");
			else
				$k += (" -k "+$i);
		}
	}
	if ( $i == 0 )
		$i = 1;
	$k += (" -k "+$i);
	$cmd += $k;
	print( $cmd + "\n" );
	string $newcurve = eval($cmd);
	return $newcurve;
}

This is a way of batch converting TEX files to TIFF format. In a terminal window in Linux, copy and paste the following bold text exactly as they appear, WITHOUT MODIFICATION.
For current dir and all recursive dir's under it use;

For current dir only, you will also need the maxdepth 1 option:

For finding only recent files, use -amin +/-N where N is in minutes and - means newer than, + older than:
Here for example, find all shadow textures rendered in the last 10 minutes.

find all .mb or .ma files that have velvet in their name

exr's less than 1 day old

exr's more than 1 day old

exr's less than 60 minutes old

This command will list all the file names in the current directory (.)
that start with c#- and end with .pdf where # is any single numeric digit

this command would find double digits ( c##- )

This command will batch download all pdf's from the specified url.
Useful to go and get all of Numerical recipes in C from the web in one
go without clicking 100 times!

The paramaters:

type "env" in the shell and it will list all of your environment variables

will pipe it into a text file so you can search it easily.

type

to login to a machine from some other workstation (so substitute machinename for whatever the workstation name is). Now it's exactly as if you were sitting there.
type

and you get a list of processes currently running on that machine. You can use the PID to pass to 'kill' to shut down processess that have hanged.
also

(lowercase 'L')

will list all of the devices that can be mounted (such as hard disks).

will mount all of the devices according to your mount file in wherever it is.

It wasn't obvious to me at first how to get my usb memory stick reader working on linux 7/9. So here's a couple of helpful links that got me on the right track

I created a directory under root called /mspro to mount my device to once i'd edited the fstab.
type

to mount it, and then;

when you want to unplug it (minus lowercase L for 'lazy'). At work i do this to mount the memory stick into /mnt/mspro/ in /etc/fstab;

then in a shell

On my home machine, I'd do this

Use;

to figure out what to add to fstab. The number of blocks will be significantly less than your hard disks, so that's how you tell what one it is.
Apparently

is a pretty useful thang too, lists hardware messages

Example - I wanted to extract f-stop info in a batch for a whole load of image files, but metacam has no command line options to do this......
'metacam' is a command line util that prints to stdout from .THM thumbnail files, all the data about an image taken with a Canon D60 camera. E.g. f-stop exposure etc. etc.
1. pipe the output of metacam on every thumbnail file into a temp text file

2. grep it to list only the important lines containing filename (they all start with CRW_) and 'aperture'

or as one line, stick a semi-colon between them (NOT an escape character)

Creates a symbolic link to /Acrobat5/bin/acroread in the directory /usr/local/bin. This is useful because /usr/local/bin is in the PATH env variable which means you can type the name of any exe's or scripts in that dir from any directory in a shell window and it will run. This effectively allows you to extent the set of Linux shell commands. Oh mental note I need to add the tiff2vnl++ script to this page, as it's well clever.

To grab the latest 2.0.x code, run the following commands:

Once you have the code downloaded, run the following commands to keep your local copy up to date:

|& pipes the results of shader into head, which in turn only displays the first few lines of output messages.... quite handy if you have billions of errors and only want to see the first couple of them.

the -print prints the file name to the stdout, this \; ends the -exec part and {} is a placeholder for the results from find

Change to the top level directory of your new software project (E.g. /u/me/dev/sw/myApp) and execute:

The important bit is to be in the correct directory and to specify a correct repository name ('maya/myPlugin' in the above case). The repository name should normally match the local directory structure and project name within your dev area, making it easier to relate the cvs repository structure to you local sub directories under whatever your $DEV path points to.
If the import succeeded then your can backup/remove your project directory. You might like to move it somewhere safe until you are sure the import worked fully. E.g. rename the direcory with a leading underscore. You can then check out the version of your project from the cvs repository back into your local working area.

To check out a project from the repository (such as the one you might have imported above) change directory to the top of your local dev area:

Because cvs checks out files into your current directory you will normally want to be in /u/dde/dev.
Then use cvs to checkout the named directory, file or files:

(will create /u/dde/dev/sw/myApp/)
After this you should have a new $DEV/maya/myPlugin directory and subsequent subdirectories. You can now go ahead and modify your source files.

After making changes to your software project and building a working version your can do the following to save any changes back to the cvs repository - Change to your project top-level directory (E.g. /u/dde/dev/sw/myApp) and type:

The current directory and all subdirectories will be scanned and changes stored. Note that you must explicitly add and remove any files using cvs (see below).

If you add any files to your checkout project you must use the following command before they can be committed:

To remove files from your project you must first remove the files from disk using 'rm' then use the following cvs command before a commit:

If someone else has committed changes to files you have checkout then you can merge those changes (as long as they're not too significant) into your local project using the following command:

To use this, type

It's an example of how to use a config file - wx-config in this case - inside a make file to get the include paths necessary.

In NEDIT; to regex find / replace

or

or

use find :

replace :

and Alt+T to replace again. You have to use () around the regular expressions in 'find' that you want to use access again later on in the substitution otherwise it won't work.

To explain a bit what

does;

consider the following sequence

to get just the basename.... "mySequence"

to get just the extension.... "exr"

to get just the frame number...."0001", "0002", etc

here's the full list of modifiers...

	h
	    Remove a trailing pathname component, leaving the head.
	t
	    Remove all leading pathname components, leaving the tail.
	r
	    Remove a filename extension \u2018.xxx\u2019, leaving the root name.
	e
	    Remove all but the extension.
	u
	    Uppercase the first lowercase letter.
	l
	    Lowercase the first uppercase letter. s/l/r/ Substitute l for r. l is simply a string like r, not a regular expression as in the eponymous ed(1) command. Any character may be used as the delimiter in place
	    of \u2018/\u2019; a \u2018\\u2019 can be used to quote the delimiter inside l and r. The character \u2018&\u2019 in the r is replaced by l; \u2018\\u2019 also quotes \u2018&\u2019. If l is empty
	    (\u2018\u2018\u2019\u2019), the l from a previous substitution or the s from a previous \u2018?s?\u2019 event specification is used. The trailing delimiter may be omitted if it is immediately followed by a newline.
	&
	    Repeat the previous substitution.
	g
	    Apply the following modifier once to each word.
	a (+)
	    Apply the following modifier as many times as possible to a single word. \u2018a\u2019 and \u2018g\u2019 can be used together to apply a modifier globally. In the current implementation, using the \u2018a\u2019
	    and \u2018s\u2019 modifiers together can lead to an infinite loop. For example, \u2018:as/f/ff/\u2019 will never terminate. This behavior might change in the future.
	p
	    Print the new command line but do not execute it.
	q
	    Quote the substituted words, preventing further substitutions.
	x
	    Like q, but break into words at blanks, tabs and newlines. 
							

This will output to the shell, all of the revision numbers associated with changes to files in this directory and their associated log message.
Use this to figure out which revision your file changed in, to enable you to checkout or diff previous versions...

The file checked out will go in whatever your current dir is, so make sure you know if something will be overwritten

As above, but getting an older version instead of the latest one

HEAD is an alias for the highest revision number for this file. You can also just put a revision number here