Yeah, it's just fewer objects, and [pix_motion_sector] reports the % of pixels that have changed in the region. That makes it easy to set up triggers with an instance of moses. I worked on that a couple years ago and haven't really thought about it until Hans posted the link. I don't mean to hijack the thread, but right now I'm interested in getting feedback on this table info/manip extern:
http://williambrent.conflations.com/pages/research.html#tabletool
I posted it on another thread earlier today and added several more functions since. Nothing that you can't do in other ways, but I think these things are useful to have easy access to:
- dumping a table to a list
- reporting the length of a table
- offsetting (adding a constant to all values)
- scaling (multiplying all values by a scalar)
- curve smoothing
- shifting values forward or back by index
- shuffling values randomly
- sorting values from low to high
- sorting a sub-range of values from low to high
- reversing
- inverting
- normalizing to a specified range
- normalizing so values sum to 1.0
- copying a source table to a target table
- copying a specified range of a source table to a target table
- lacing alternating values from two tables into one table
- table sum
- table mean
- table arithmetic mean
- table geometric mean
- table integration
- table differentiation
- adding two tables
- subtracting two tables
- multiplying two tables
- dividing two tables
- dot product between two tables
- Euclidean distance between two tables
- Manhattan distance between two tables
- Pearson correlation coefficient between two tables
- reporting minimum value (and its index)
- reporting maximum value (and its index)
- reporting the closest value in the table to a given value (and its index)
- number of occurrences of a given value (and a list of their indices)
- number of occurrences of a value less than a given value (and a list
of their indices)
- number of occurrences of a value greater than a given value (and a
list of their indices)
On Thu, May 13, 2010 at 7:40 PM, Mathieu Bouchard matju@artengine.ca wrote:
On Thu, 13 May 2010, William Brent wrote:
Yes - it's exactly that: an adaptation of pix_movement that lets you specify an area to analyze. That way you can use several instances to create multiple regions for triggering different events. I haven't looked at this in two years! I'll take a look at the helpfile and see what's missing/unclear.
what's the difference between that, and using [pix_crop] and [pix_movement] with [pix_separator] ?
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801