CNMAT Flashback

A look back at some items in our archives.

Archive Browser

Browse CNMAT content by type
Book page

Syllabus

We will survey sensor types covered include:
resistive, position, inertial, capacitive, RF, ultrasound, magnetic and optical.

Build sensors from fabric

We will explore the major sensor integration systems, e.g., Make Controller Kit, Arduino, and CUI,

How to adapt existing sensors such as the Nintendo Wii controllers.

Book page

Interactive multitouch hemispherical dome

Build a hemispherical dome version of the idea with a fisheye lens. This has better ergonomy for collaborative use of a surface since you are not bent over a coffee table and can have eye to eye contact with other people around the dome and it could be done on a large scale (e.g. at the exploratorium).

Book page

Troubleshooting

Troubleshooting

"Operation Timed Out"

Once when I tried to commit some changes to the repository I
saw this:

Book page

Introducation and Preparing for the workshop

I am looking forward to meeting you all next week for the sensor workshop. As well as the lectures and workshop time we will be doing at least one field trip and will enjoy guest lectures and performances of state of the art sensor instruments including David Wessel's new instrument introduced at NIME2007 last month.

Book page

Best Practices for using version control

Never store "derived" files in version control. Check in only source files, makefiles, etc.; the results of the build process (.o files, executable files, Java .class files, etc.) should not be under version control.

Book page

Dealing with bad characters in filenames

## Leading minus signs

If a filename begins with "-", like "-foo", then SVN commands will think you're supplying a command-line option when you're really trying to give the name of the file.

Solution: refer to the file as ./-foo, as in

svn mv ./-foo +foo

## Umlauts

SVN fails in an ugly way when you try to check out a file with an umlaut in its name.

Book page

Version numbers

## Version numbers

Each external should include its version number as described [cnmat:node/272|here]. Packages of patches that we release with the old new Max downloads page can have their version and other information in the same format in a separate "infosource.txt" file.

Book page

Authorship, License, Copyright, and Disclaimer

##

Every patch or [cnmat:node/272|textual source code file] should contain a comment listing the names of the authors and the year(s) it was written.

Software developed by CNMAT students, faculty, and staff almost always belongs to the University.

Book page

Help patches

Each patch or external should have a help patch listing all of its features. The help patch should show how the object would be used in context and designed for easy cut and paste.

For a file named something.pat, something.mxb, or something.mxt, its help patch should be named something.help.pat

A generic help file can be found in the repository in /MMJ-Depot/baseline/support/

Book page

Generic OSC-Style Messages

While not every patch implements all of these messages, these are some very common and desirable messages for a patch to understand:

  • /gain Controls the Linear Amplitude of the signal output. Should accept an optional second argument to change to a specific amplitude over a number of milliseconds.

Pages