I'm using MoveMapper developed by Nicholas Felton to viz the data collected by the Moves for iPhone App.
However, I get the following error message after obtain the accessToken from Moves website according to Nicholas' guide on Github for MoveMapper (
https://github.com/feltron/MMapper)
I have a very simple Processing code shown below. However, after I export it as windows application, the 32bit version gave me an error, and the 64bit version don't show up at all (a terminal window flashed quickly and disappear... )
I don't understand why the "double buffering" version of the code shown below doesn't seem to improve the rendering significantly as compared with the "non double buffering" version according to frame rate ...
Appreciate your advices on:
1. Am I using "double buffering" correctly?
2. how to get the points shown on top of the lines?
I remember someone has written a processing library (or wrapper) for the lighting simulation software Radiance (
http://ww.radiance-online.org/). But I don't remember where it is....
May I ask how the following script can be revised using double-buffering technique so that it can run more smoothly when a far larger amount of points (say, 10000) are generated ? especially how this technique should be applied on each mover object's display method level?
Thanks!
code reference: Daniel Shiffman's The Nature of Code exercise_2_1
// keys:
// [space] : toggle animation
Mover[] movers = new Mover[100];
boolean animationToggle = false;
void setup(){
size(700,350);
for(int i=0; i<movers.length; i++){
movers[i] = new Mover(random(0.5,3),random(0,width),random(0,height),
... in which, "render" is the program, "-n 8" is one of its parameter (number of CPU cores) and the value associated with it, "A.txt" is a base file, "B.txt" is the input file, "C.txt" is the output file.
I've tried the following but none can get the shell script run as it runs in the terminal ...
Plus, for those using Processing 2.0b8, the following code need to be added:
import java.net.*;
import java.io.*;
import java.util.Calendar;
import java.util.Iterator;
I'd like to draw the trail for each of a group of bouncing points, but I can't get it work by using begainShape/endShape. No continuous line segments are created, instead points are still shown as individual points.
I assume the problem is related to the arraylist to store position history ...
I got the following error when running a code in Processing 2.0b8 in Mac OS, whereas the same code runs with no problem in Processing 2.0b8 in Windows7 ...
I found that after updating the latest PeasyCam library, the size of point/line as shown in 3D scene is always relative rather than absolute. i.e. the size of a point/line as shown on screen is always the same no matter you zoom in or out.
Is it related to the update of Processing (2.0b8) or PeasyCam?