Ripple home
tech specs + budget
the artists
work samples
 

Tech Specs + Budget

   
 
 

Turbulence Server Specs

Please provide a concise description of the project's technical aspects.

The primary components of the web-based portion of Ripple will be a client-side Java applet and a series of server-side Perl scripts. 

  • A Perl scripts will be fetching images from flickr.com periodically.
  • Another will be acting as a communication server, receiving live seimsic information either directly through LISS software (http://www.liss.org) running on the Turbulence server or from another server running the LISS software (see below).
  • A perl script will also be used to apply distortions to imagery, combining previous imagery, new imagery and seismic data.
  • A final Perl script will be broadcasting information in real-time to active copies of the Java applet (people who are viewing the work at any given moment) where combined effects of the work are made visible.

Besides a standard Perl distribution, Image Magick and the Image Magick Perl module will need to be installed as well as GD and the GD Perl module for additional image manipulation. Perl, Image Magick and GD are all open-source products available for free download on the Internet. My experience has shown me that it works well to do these sorts of tasks in a modular manner, which is why the project runs as several Perl scripts instead of being combined into one. That way if anything does go wrong, that single process is killed and restarted without it having a noticeable effect at the viewer's end. The initial startup of the project and continued maintenance of it's component scripts are controlled by bash scripts.

As a secondary component, we will likely maintain a surf-able archive of unprocessed as well as processed imagery from all three spaces using PHP and MySQL.

What portion of the project will be realized on the turbulence.org server? Be specific, including figures on disk usage and memory requirements. Be sure to characterize the impact on the the server (i.e. sporadic CGI scripts vs a constant daemon process running in the background). Also include figures on the number of people in your project who would need access to the turbulence.org server, and in what manner (ftp access, shell access, etc.).

We would like to house as much as possible on the Turbulence servers. If running the Perl communications server (which would need to run as a daemon process) is a problem, this can be run on another server. However, this would mean that the Java applet would need to be served from the same server as Java security measures do not allow applets to connect to server applications on computers other than the one that served the applet. If it is necessary to do this, the Java applet can appear in a frame so that the page will still appear to originate from the Turbulence server (will be accessible via a turbulence.org/ripple URL). If required, components of the work will be housed on the server pallit.lhi.is in Iceland.

What portion of the project (if any) will be realized on server(s) other than turbulence.org? Please describe this specifically and characterize the interaction between the servers.

If possible, please state the approximate monthly bandwidth you anticipate using for this project.

The size of the Java applet is not expected to exceed 200kb and the total size of other elements of the website should not exceed 150kb. Therefore a total of 350kb will be served for each hit. Aside from this, there will be constant communication between the Java applet and the server. It is hard to say how much this will be. Some bandwidth will also be required to receive seismic data and to retrieve imagery. Again, it is hard to say what this will amount to.

Computers in the Arts Interactive installation will be uploading imagery from the physical installation as well as the Ars Virtua installation via FTP. The rate of images being uploaded will be 3 to 5 images per day at a size of approximately 150 kb for the duration of the installation (30 days).

 

 

 

turbulence specs
ars virtua specs
art interactive specs
budget
back to top

 
 

Ars Virtua Specs

Will you work within the existing SL structure or do you plan to create something unique?

Ripple will use a combination of standard avatars bots, libsecondlife, and a custom application in order to alter appearance in real time. We should be able to accomplish this with our own skill sets, but have budgeted for external help, if necessary.

How will the Ars Virtua component of your project interface with the Turbulence and Art Interactive components?

All three spaces will be distorting "bodies" in real time, using live feeds of seismic data from the internet. Additionally, there will be live images and linkages from all three spaces both online and in Ars Virtua (Art Interactive will display the other two spaces on monitors next to its installation). It should also be noted that the sculptures in Art Interactive will be replicas of our avatar, whose moulds will be produced using OGLE and a 3D printer.

Will the realization or your piece fit into the 2000 m sq of Ars Virtua's main Gallery and within 500 prims?

Yes.

Will you be streaming video or audio into the space? How many streams will you be using, and have you done this before?

We will not be using live audio or video. We will have static, updated image/links from the online (turbulence) documentation of the other two spaces, using simple, embedded URLs

 

turbulence specs
ars virtua specs
art interactive specs
budget
back to top

 
 

Art Interactive Specs

What are the dimensions of the piece?

Approximately 10 x 10 x 4 feet

What equipment will it require? Are you able to supply the equipment?

We will simply require a PC, web cam and internet connections for the main installation - preferably a mac, which could more easily take regular photos and upload them to the web (Turbulence server). If the option is available, we'd also like to display our SL and Turbulence works alongside the AI piece, with separate computers and monitors. The computer displaying the SL installation will also be used to generate screenshots to upload to the web for use in the Turbulence component of the work. Uploading will be automated with Perl scripts. Mac OS X and most Linux distributions install Perl by default. However, in the case of a Windows PC, Perl can be downloaded from the Internet for free. We can provide the web cam.

Other installation materials?

Wax "bodies," lights (or some other device to melt the wax), and some physical computing hardware – all of this will be provided by the artists.

Will anything have to be suspended from the ceiling?

Perhaps the lights, but most likely we'll build a sculptural stand for this.

How will the piece be delivered to Art Interactive?

Either in person or by courier.

How will the piece be installed and by whom? How long will the installation take?

One or both of the artists will install the work, and it should take no more than 2 days, but we'd like 3 or 4, if possible, just in case.

 

turbulence specs
ars virtua specs
art interactive specs
budget
back to top

 
 

Budget

$500: production of sculpture mould
$1000: production of wax avatars
$250: any necessary shipping
$200: various physical computing gadgets (relays, lights for melting, etc)
$100: rig for lights
$1250: budget for additional consulting / programming fees as needed
$1300: travel to Boston from Iceland and Ireland
$400: shared room for 4 nights in Boston
$2000: artist fees

Total: $7,000*
*Note that we are looking for additional funding and, should we fail to get it,
we will forfeit our artist fees, bringing the budget down to $5000

 

turbulence specs
ars virtua specs
art interactive specs
budget
back to top