Freeside Atlanta - User contributions [en]

Delta 36-430 Table Saw

2014-09-09T23:05:33Z

Steamboat: /* Warnings */

Delta 36-430 Table Saw

2014-09-09T23:03:55Z

Steamboat: /* Caution */

Delta 36-430 Table Saw

2014-09-09T23:03:38Z

Steamboat: /* Caution */

Delta 36-430 Table Saw

2014-09-09T23:03:22Z

Steamboat: /* Caution */

Delta 36-430 Table Saw

2014-09-09T23:03:02Z

Steamboat: /* Caution */

Delta 36-430 Table Saw

2014-09-09T23:02:23Z

Steamboat: /* Caution */

Delta 36-430 Table Saw

2014-09-09T22:17:38Z

Steamboat: /* Caution */

[[File:ImageOfEquipment.jpg|thumb|300px]]

= Zone =
[[Equipment]] \ [[Warehouse]] \ [[Woodshop]]

= About =
What is this equipment used for. Brief description.

Replacement blade guard assembly Delta Part A23469

= Owner(s) =
* Freeside

= Hackability =
Hack/Do Not Hack/List Of Desired Improvements

== Permissions ==
Rules and expectations for use of this piece of equipment. Example: 
For general use by members after they have completed an appropriate training course. Treat this equipment as if it were your own cleaning items off of the top of the machine and around its table after usage.

== Restrictions ==
Things the equipment shouldn't be used for, limitations, etc (Don't grind aluminum or brass, etc) 

== Caution ==
Things a user should know prior to using the equipment: 

Do not wear gloves while operating a table saw. There are several reasons, but loss of tactile sense is probably foremost, while a possible loss of gripping power is also close to the top. And some kinds of gloves are loose enough to present an item for the rotating blade to grab.

Keep the floor in front of the saw free of cut-offs and piled up sawdust. Tripping or sliding into a running, or even stopped, saw blade can really create problems, but even slipping and banging your head against the cast iron table can bring on a bad injury.

Wear proper eye and hearing protection. Eyes need to be protected from damage by projectiles--and no, standard eyeglasses will not do the job. Hearing protection is something every woodworker should start with, and continue. Hearing loss creeps up on you without warning, and often without symptoms, until it's too late to reverse the procedure.

Wear short sleeves, leave the ties at the office, and junk your dangling jewelry. Get rid of other loose fitting clothing while operating a table saw. Any of these items might get caught in the blade and yank you into it before you can react. Stand comfortably, with your feet far enough apart for good balance. This is always important, but more so when you're cutting stock long enough to require several steps towards the saw to keep the feed going. Then, you build up momentum and want to be able to stop easily. Wear footwear with non-slip soles.

Stand comfortably, with your feet far enough apart for good balance. This is always important, but more so when you're cutting stock long enough to require several steps towards the saw to keep the feed going. Then, you build up momentum and want to be able to stop easily. Wear footwear with non-slip soles.

Avoid any awkward operations. If you feel like a gawky fool doing a cut, then don't do the cut in that manner. This helps you avoid losing your balance and possibly falling into the blade or table.

Use a push stick to cut stock that is 6" or less in width. A hand that isn't close to a blade isn't going to get cut. Generally, a 6” minimum distance to the blade is considered safe, though some recommend 4”.

Use a stop block when you crosscut short lengths. Mount a stop block on the fence--this can be as simple as a clamped on board that stops just before the saw blade, so that cut-off pieces cannot bind between blade and fence.

Position your body so that it is NOT in line with the blade. This keeps sawdust feeding back through the slot of the blade out of your face, and much more important, it keeps you out of the line of most kick-backs.

Never reach behind or over the blade unless it has stopped turning. Sometimes this looks safe. It almost never truly is. This does not mean you should stop pushing your work before it finishes passing through the blade, itself an invitation to kick back.

Always disconnect the power before changing the blade or performing any other maintenance operation. I like to drape the plug over my fence rail so I know in an instant the saw's unplugged…or not.

Make sure that the blade has stopped turning before you adjust the table saw. The reasons are obvious. Making adjustments can get hands too close to the blade, and even a slowly spinning blade has a multitude of sharp edges that can do damage. Always make sure that the blade is turning free before you turn on the power: this is especially helpful after you make changes or adjustments. In other words, spin the blade without power a time or two to make sure there are no scraps or tools touching it.

Keep the tabletop smooth and polished. A dirty or rough table requires you to use more force to push the stock through the blade. It may also rust like crazy, further reducing the saw's effectiveness.

Keep the rip fence parallel to the blade so stock doesn't bind on the blade and kick back. Some woodworkers prefer to keep the rear of the fence kicked out (away from the blade) by 1/64". I believe parallel is better, but a friend of mine, with more experience than I, keeps the back of his fence kicked out. Both work.

Use zero clearance inserts. These reduce the chance of slender cuts dropping into the lower part of the blade and making the round trip to speed by your head. They also reduce splintering in cuts.

Never operate a table saw with the throat insert removed. Wood that is fed into a gaping hole can drop down and get caught on the blade. That can't happen if the throat insert is in place.

Do not make free-hand cuts on a table saw. Guide the stock through the blade using the rip fence or the miter gauge.

Keep the blade guards, splitters and anti-kickback fingers in place and operating freely. Check the action of these items before starting work.

Work should be released only when it is past the blade. Releasing work too early is an invitation to kickback as it is possible for the blade to grab the part that has not yet gone by.

Whenever the stock is lifted or tilted above the surface of the table, the saw is able to shake the stock. If this happens, and you lose your grip, duck down and hit the stop button because losing your grip on the work means it probably is going to come back at you.

Check stock before cutting. Look for nails, knots, screws, or stones. Such fun items may become projectiles. If they hit, they smart, and may cause serious injury as well. Also, damage to carbide tipped blades can be major, even if all it does is scare you.

The fence and the miter gauge are not meant to be used together. Under some circumstances, you can use both (see above on stop blocks), but the fence then needs an auxiliary fence added. That fence or stop must end just before the saw blade.

Don't mess with the fence adjustment when the saw is running. And a general addition, which goes for all tools and all techniques in a wood shop: if a procedure feels unsafe, it probably is, so don't use it. Find another way to do what has to be done.

= Basic Instructions =
* Step 1
* Step 2

== Specifications and Detailed Instructions ==
[[File:Info.jpg|50px|link=http://10rem.net/hobbies/woodworking/delta-contractors-saw-rebuild---the-frankensaw]]URL to excellent teardown and maintenance walk-through 
[[File:RTFM.PNG|50px|link=http://www.1800toolrepair.com/schematics/36-430_TYPE_1.pdf]]URL to product manuals 
[[File:Video.jpg|50px|link=http://bcove.me/6k8vlh1x]]Link to videos showing good examples of use

= Tips =
* ??
* ??

= Warnings =
Delete those that do not apply 

[[File:Laser.PNG|100px]] Eyesight Damage Risk

[[File:Entrapment.png|100px]] Entrapment Risk

[[File:Flammable.png|100px]] Flammable Risk

[[File:HighSpeedMovingParts.png|100px]] High Speed Moving Parts

[[File:NonIoizingRadiation.png|100px]] Non-Ionizing Radiation (RF)

[[File:UV.png |100px]] UV Radiation

[[File:Radiation.PNG |100px]] Radiation Warning

[[File:Poison.PNG|100px]] Poisonous Substances

[[File:Hot.gif|100px]] Hot Surfaces

[[File:Cutting.PNG|100px]] Cutting Risk

[[File:Crush.png|100px]] Crush and Pinch Risk

[[File:ElectricShock.PNG|100px]] Electric Shock Risk

[[File:ElectricShock.PNG|100px]] High Voltage

== Safety ==
Delete those that do not apply 

[[File:BreathingMask.PNG|100px]] Breathing Mask Required

[[File:Gloves.PNG|100px]] Gloves Required

[[File:Goggles.PNG|100px]] Eye Protection Required

[[File:HardHat.PNG|100px]] Hardhat Required

[[File:Hearing.PNG|100px]] Hearing Protection Required

[[File:Lockout.PNG|100px]] Lockout Required

[[File:RTFM.PNG|100px]] Read the Fine Manual

[[File:Unplug.PNG |100px]] Unplug After Use

[[File:WashHands.PNG|100px]] Wash Hands Prior/After Use

[[File:Unplug.PNG |100px]] Unplug After Use

[[File:WeldingMask.PNG |100px]] Welding Mask Must Be Worn

[[category: Equipment]]
[[category: QR Code Needed]]

Delta 36-430 Table Saw

2014-09-09T22:17:08Z

Steamboat: /* Restrictions */

Delta 36-430 Table Saw

2014-09-09T22:13:49Z

Steamboat: /* Specifications and Detailed Instructions */

Delta 36-430 Table Saw

2014-09-09T22:11:21Z

Steamboat: /* Specifications and Detailed Instructions */

Delta 36-430 Table Saw

2014-09-09T21:57:21Z

Steamboat:

Delta 36-430 Table Saw

2014-09-09T21:54:42Z

Steamboat:

[[File:ImageOfEquipment.jpg|thumb|300px]]
To use this template, copy <code><nowiki>{{subst:EquipmentPage}}</nowiki></code> into a new page, save, and then begin editing. The current version of this template will be copied into the new page. Future modifications to this template will change existing pages. 
Add or link new equipment pages to [[Equipment]]
= Zone =
(Set to the right zone) 
[[Equipment]] \ [[Warehouse]] \ [[Metal Shop]]

= About =
What is this equipment used for. Brief description.

= Owner(s) =
* Freeside
* Member Name (Link to their Wiki Page if it exists)

= Hackability =
Hack/Do Not Hack/List Of Desired Improvements

== Permissions ==
Rules and expectations for use of this piece of equipment. Example: 
For general use by members after they have completed an appropriate training course. Treat this equipment as if it were your own cleaning items off of the top of the machine and around its table after usage.

== Restrictions ==
Things the equipment shouldn't be used for, limitations, etc (Don't grind aluminum or brass, etc) 
* ??
* ??

== Caution ==
Things a user should know prior to using the equipment (turn on power supply prior to plugging in USB, etc) 
* ??
* ??

= Basic Instructions =
* Step 1
* Step 2

== Specifications and Detailed Instructions ==
[[File:Info.jpg|50px|link=]]URL to product page if it exists 
[[File:RTFM.PNG|50px|link=]]URL to product manuals 
[[File:Video.jpg|50px|link=]]Link to videos showing good examples of use

= Tips =
* ??
* ??

= Warnings =
Delete those that do not apply 

[[File:Laser.PNG|100px]] Eyesight Damage Risk

[[File:Entrapment.png|100px]] Entrapment Risk

[[File:Flammable.png|100px]] Flammable Risk

[[File:HighSpeedMovingParts.png|100px]] High Speed Moving Parts

[[File:NonIoizingRadiation.png|100px]] Non-Ionizing Radiation (RF)

[[File:UV.png |100px]] UV Radiation

[[File:Radiation.PNG |100px]] Radiation Warning

[[File:Poison.PNG|100px]] Poisonous Substances

[[File:Hot.gif|100px]] Hot Surfaces

[[File:Cutting.PNG|100px]] Cutting Risk

[[File:Crush.png|100px]] Crush and Pinch Risk

[[File:ElectricShock.PNG|100px]] Electric Shock Risk

[[File:ElectricShock.PNG|100px]] High Voltage

== Safety ==
Delete those that do not apply 

[[File:BreathingMask.PNG|100px]] Breathing Mask Required

[[File:Gloves.PNG|100px]] Gloves Required

[[File:Goggles.PNG|100px]] Eye Protection Required

[[File:HardHat.PNG|100px]] Hardhat Required

[[File:Hearing.PNG|100px]] Hearing Protection Required

[[File:Lockout.PNG|100px]] Lockout Required

[[File:RTFM.PNG|100px]] Read the Fine Manual

[[File:Unplug.PNG |100px]] Unplug After Use

[[File:WashHands.PNG|100px]] Wash Hands Prior/After Use

[[File:Unplug.PNG |100px]] Unplug After Use

[[File:WeldingMask.PNG |100px]] Welding Mask Must Be Worn

[[category: Equipment]]
[[category: QR Code Needed]]

Delta 36-430 Table Saw

2014-09-09T21:54:27Z

Steamboat:

<code><nowiki>{{subst:EquipmentPage}}</nowiki></code>

Freeside Braniacs

2014-04-11T02:26:54Z

Steamboat: /* Python to Arduino Interface */

Brainiacs is a meetup that is all about Neuroscience and Brain-Computer Interfaces.

The first round of projects that we've been working on center around setting up interfaces between different BCI and biometric devices with Python so that it will be much easier to build systems and collect data.

== NeuroSky to Python Interface ==

One of the major points of discussion in the last meeting was how to identify and solve for the individual interfaces to collect biometric data and then push it to other systems like databases or arduinos to act on the data. Here is my walkthrough for the interface between the NeuroSky and Python.

If you're in Windows and haven't fooled around with Python yet and would like a soft introduction, here is my recommendation. This is what I use because I have to do this stuff on my work computer too so it's just easier to manage everything in Windows 7 for me. If you're in Linux then this stuff is way easier for you and you'll probably be using a toolkit of choice there anyway.

1 - Install pythonxy. This is an excellent package for Python in Windows that includes most of the important scientific computing libraries all at once, as well as pip and easy_install (package managers) and iPython Notebook (which is what I use). It also has pandas, opencv, scikits-learn, simpy, and of course numpy and scipy. Apparently it has the necessary tools to build a gui too, but I haven't gotten that far yet.

Uninstall whatever python stuff you have on your computer before installing this so you don't end up with multiple weird instances.

2 - Press windows_key+r to bring up the run dialogue. Type cmd to bring up the command prompt.

3 - Learn how to use the console. You could go through the trouble of learning powershell or using cygwin if you want, but I only use the command prompt to launch ipython and easy_install anyway. I'd rather invest my spare time learning bash, though I'm still pretty terrible at it.

4 - type ipython notebook in whatever folder you want to store your code.

5 - It will bring up your default browser and you can write your code in "cells" that execute individually on a specific kernel for each tab or "notebook." It's really easy.

6 - In the console, type easy_install neuropy and it will pull down the library and set it up for you.

7 - The documentation for the NeuroPy library is pretty easy to read and enough to get you started.

Now, even if you don't have a NeuroSky, you can start to build programs to simulate the generation of the data and what to do with it so that when we hook up the device, we'll just be able to plug in and go. I've tested it with my NeuroSky and was able to replicate the functionality show in the documentation I linked to above.

The python library is much easier to connect to the NS than the phone or tablet apps, which I've found excruciatingly frustrating.

== Python to Arduino Interface ==

Here is some info that I dug up about getting an arduino to talk to python and vice-versa. (Sorry for the formatting. MediaWiki is being kind of a nightmare about this)

For my solution, it worked to send data in two-byte packages. So python basically sends a header and then a 0-255 value with something like:

import serial

port = 'COM6'

baudrate = 9600

arduino = serial.Serial(port, baudrate)

val1 = 255

arduino.write('h' + chr(int(val1)))

void setup() {
Serial.begin(9600);
}

void loop() {
if(Serial.available() >= 2){
switch( byte( Serial.read() )) {
case 'r':
colorRGB[0] = Serial.read();
blnFade = 0;
break;
case 'g':
colorRGB[1] = Serial.read();
blnFade = 0;
break;
case 'b':
colorRGB[2] = Serial.read();
blnFade = 0;
break;
case 'c':
Serial.flush();
blnFade = 0;
break;
case 'f':
delayVal = Serial.read();
Serial.flush();
colorFade();
blnFade = 1;
}
}

Where it is looking for a "mode" and then runs a function afterwards that may or may not use the second value (it runs serial.flush() when it doesn't need the second character).

There is some more data available at the following links and I'll be working on it this week to make a mind-controlled AR Drone or RC Car for the Atlanta Science Festival next weekend. I may even get to the point where I can make the controls that supplement the NeuroSky run through a Leap Motion if I have time.

http://playground.arduino.cc/interfacing/python#.Uy4SaPldXSA
http://www.instructables.com/id/Arduino-and-Python/?ALLSTEPS
http://forum.arduino.cc/index.php/topic,8332.0.html

Soon, we're gonna have a pretty awesome platform!

Freeside Braniacs

2014-04-06T21:49:28Z

Steamboat:

Brainiacs is a meetup that is all about Neuroscience and Brain-Computer Interfaces.

The first round of projects that we've been working on center around setting up interfaces between different BCI and biometric devices with Python so that it will be much easier to build systems and collect data.

== NeuroSky to Python Interface ==

One of the major points of discussion in the last meeting was how to identify and solve for the individual interfaces to collect biometric data and then push it to other systems like databases or arduinos to act on the data. Here is my walkthrough for the interface between the NeuroSky and Python.

If you're in Windows and haven't fooled around with Python yet and would like a soft introduction, here is my recommendation. This is what I use because I have to do this stuff on my work computer too so it's just easier to manage everything in Windows 7 for me. If you're in Linux then this stuff is way easier for you and you'll probably be using a toolkit of choice there anyway.

1 - Install pythonxy. This is an excellent package for Python in Windows that includes most of the important scientific computing libraries all at once, as well as pip and easy_install (package managers) and iPython Notebook (which is what I use). It also has pandas, opencv, scikits-learn, simpy, and of course numpy and scipy. Apparently it has the necessary tools to build a gui too, but I haven't gotten that far yet.

Uninstall whatever python stuff you have on your computer before installing this so you don't end up with multiple weird instances.

2 - Press windows_key+r to bring up the run dialogue. Type cmd to bring up the command prompt.

3 - Learn how to use the console. You could go through the trouble of learning powershell or using cygwin if you want, but I only use the command prompt to launch ipython and easy_install anyway. I'd rather invest my spare time learning bash, though I'm still pretty terrible at it.

4 - type ipython notebook in whatever folder you want to store your code.

5 - It will bring up your default browser and you can write your code in "cells" that execute individually on a specific kernel for each tab or "notebook." It's really easy.

6 - In the console, type easy_install neuropy and it will pull down the library and set it up for you.

7 - The documentation for the NeuroPy library is pretty easy to read and enough to get you started.

Now, even if you don't have a NeuroSky, you can start to build programs to simulate the generation of the data and what to do with it so that when we hook up the device, we'll just be able to plug in and go. I've tested it with my NeuroSky and was able to replicate the functionality show in the documentation I linked to above.

The python library is much easier to connect to the NS than the phone or tablet apps, which I've found excruciatingly frustrating.

== Python to Arduino Interface ==

Here is some info that I dug up about getting an arduino to talk to python and vice-versa.

For my solution, it worked to send data in two-byte packages. So python basically sends a header and then a 0-255 value with something like:

import serial

port = 'COM6'

baudrate = 9600

arduino = serial.Serial(port, baudrate)

val1 = 255

arduino.write('h' + chr(int(val1)))

void setup() {
Serial.begin(9600);
}

void loop() {
if(Serial.available() >= 2){
switch( byte( Serial.read() )) {
case 'r':
colorRGB[0] = Serial.read();
blnFade = 0;
break;
case 'g':
colorRGB[1] = Serial.read();
blnFade = 0;
break;
case 'b':
colorRGB[2] = Serial.read();
blnFade = 0;
break;
case 'c':
Serial.flush();
blnFade = 0;
break;
case 'f':
delayVal = Serial.read();
Serial.flush();
colorFade();
blnFade = 1;
}
}

Where it is looking for a "mode" and then runs a function afterwards that may or may not use the second value (it runs serial.flush() when it doesn't need the second character).

There is some more data available at the following links and I'll be working on it this week to make a mind-controlled AR Drone or RC Car for the Atlanta Science Festival next weekend. I may even get to the point where I can make the controls that supplement the NeuroSky run through a Leap Motion if I have time.

http://playground.arduino.cc/interfacing/python#.Uy4SaPldXSA
http://www.instructables.com/id/Arduino-and-Python/?ALLSTEPS
http://forum.arduino.cc/index.php/topic,8332.0.html

Soon, we're gonna have a pretty awesome platform!

Freeside Braniacs

2014-04-06T21:48:40Z

Steamboat:

Brainiacs is a meetup that is all about Neuroscience and Brain-Computer Interfaces.

The first round of projects that we've been working on center around setting up interfaces between different BCI and biometric devices with Python so that it will be much easier to build systems and collect data.

== NeuroSky to Python Interface ==

One of the major points of discussion in the last meeting was how to identify and solve for the individual interfaces to collect biometric data and then push it to other systems like databases or arduinos to act on the data. Here is my walkthrough for the interface between the NeuroSky and Python.

If you're in Windows and haven't fooled around with Python yet and would like a soft introduction, here is my recommendation. This is what I use because I have to do this stuff on my work computer too so it's just easier to manage everything in Windows 7 for me. If you're in Linux then this stuff is way easier for you and you'll probably be using a toolkit of choice there anyway.

1 - Install pythonxy. This is an excellent package for Python in Windows that includes most of the important scientific computing libraries all at once, as well as pip and easy_install (package managers) and iPython Notebook (which is what I use). It also has pandas, opencv, scikits-learn, simpy, and of course numpy and scipy. Apparently it has the necessary tools to build a gui too, but I haven't gotten that far yet.

Uninstall whatever python stuff you have on your computer before installing this so you don't end up with multiple weird instances.

2 - Press windows_key+r to bring up the run dialogue. Type cmd to bring up the command prompt.

3 - Learn how to use the console. You could go through the trouble of learning powershell or using cygwin if you want, but I only use the command prompt to launch ipython and easy_install anyway. I'd rather invest my spare time learning bash, though I'm still pretty terrible at it.

4 - type ipython notebook in whatever folder you want to store your code.

5 - It will bring up your default browser and you can write your code in "cells" that execute individually on a specific kernel for each tab or "notebook." It's really easy.

6 - In the console, type easy_install neuropy and it will pull down the library and set it up for you.

7 - The documentation for the NeuroPy library is pretty easy to read and enough to get you started.

Now, even if you don't have a NeuroSky, you can start to build programs to simulate the generation of the data and what to do with it so that when we hook up the device, we'll just be able to plug in and go. I've tested it with my NeuroSky and was able to replicate the functionality show in the documentation I linked to above.

The python library is much easier to connect to the NS than the phone or tablet apps, which I've found excruciatingly frustrating.

== Python to Arduino Interface ==

Here is some info that I dug up about getting an arduino to talk to python and vice-versa.

For my solution, it worked to send data in two-byte packages. So python basically sends a header and then a 0-255 value with something like:

import serial
port = 'COM6'
baudrate = 9600
arduino = serial.Serial(port, baudrate)

val1 = 255
arduino.write('h' + chr(int(val1)))

...so that the arduino grabs the data like this:

void setup() {
Serial.begin(9600);
}

void loop() {
if(Serial.available() >= 2){
switch( byte( Serial.read() )) {
case 'r':
colorRGB[0] = Serial.read();
blnFade = 0;
break;
case 'g':
colorRGB[1] = Serial.read();
blnFade = 0;
break;
case 'b':
colorRGB[2] = Serial.read();
blnFade = 0;
break;
case 'c':
Serial.flush();
blnFade = 0;
break;
case 'f':
delayVal = Serial.read();
Serial.flush();
colorFade();
blnFade = 1;
}
}

Where it is looking for a "mode" and then runs a function afterwards that may or may not use the second value (it runs serial.flush() when it doesn't need the second character).

There is some more data available at the following links and I'll be working on it this week to make a mind-controlled AR Drone or RC Car for the Atlanta Science Festival next weekend. I may even get to the point where I can make the controls that supplement the NeuroSky run through a Leap Motion if I have time.

http://playground.arduino.cc/interfacing/python#.Uy4SaPldXSA
http://www.instructables.com/id/Arduino-and-Python/?ALLSTEPS
http://forum.arduino.cc/index.php/topic,8332.0.html

Soon, we're gonna have a pretty awesome platform!

Freeside Braniacs

2014-04-06T21:48:00Z

Steamboat:

Brainiacs is a meetup that is all about Neuroscience and Brain-Computer Interfaces.

The first round of projects that we've been working on center around setting up interfaces between different BCI and biometric devices with Python so that it will be much easier to build systems and collect data.

== NeuroSky to Python Interface ==

One of the major points of discussion in the last meeting was how to identify and solve for the individual interfaces to collect biometric data and then push it to other systems like databases or arduinos to act on the data. Here is my walkthrough for the interface between the NeuroSky and Python.

If you're in Windows and haven't fooled around with Python yet and would like a soft introduction, here is my recommendation. This is what I use because I have to do this stuff on my work computer too so it's just easier to manage everything in Windows 7 for me. If you're in Linux then this stuff is way easier for you and you'll probably be using a toolkit of choice there anyway.

1 - Install pythonxy. This is an excellent package for Python in Windows that includes most of the important scientific computing libraries all at once, as well as pip and easy_install (package managers) and iPython Notebook (which is what I use). It also has pandas, opencv, scikits-learn, simpy, and of course numpy and scipy. Apparently it has the necessary tools to build a gui too, but I haven't gotten that far yet.

Uninstall whatever python stuff you have on your computer before installing this so you don't end up with multiple weird instances.

2 - Press windows_key+r to bring up the run dialogue. Type cmd to bring up the command prompt.

3 - Learn how to use the console. You could go through the trouble of learning powershell or using cygwin if you want, but I only use the command prompt to launch ipython and easy_install anyway. I'd rather invest my spare time learning bash, though I'm still pretty terrible at it.

4 - type ipython notebook in whatever folder you want to store your code.

5 - It will bring up your default browser and you can write your code in "cells" that execute individually on a specific kernel for each tab or "notebook." It's really easy.

6 - In the console, type easy_install neuropy and it will pull down the library and set it up for you.

7 - The documentation for the NeuroPy library is pretty easy to read and enough to get you started.

Now, even if you don't have a NeuroSky, you can start to build programs to simulate the generation of the data and what to do with it so that when we hook up the device, we'll just be able to plug in and go. I've tested it with my NeuroSky and was able to replicate the functionality show in the documentation I linked to above.

The python library is much easier to connect to the NS than the phone or tablet apps, which I've found excruciatingly frustrating.

== Python to Arduino Interface ==

Here is some info that I dug up about getting an arduino to talk to python and vice-versa.

For my solution, it worked to send data in two-byte packages. So python basically sends a header and then a 0-255 value with something like:

{
import serial
port = 'COM6'
baudrate = 9600
arduino = serial.Serial(port, baudrate)

val1 = 255
arduino.write('h' + chr(int(val1)))

...so that the arduino grabs the data like this:

void setup() {
Serial.begin(9600);
}

void loop() {
if(Serial.available() >= 2){
switch( byte( Serial.read() )) {
case 'r':
colorRGB[0] = Serial.read();
blnFade = 0;
break;
case 'g':
colorRGB[1] = Serial.read();
blnFade = 0;
break;
case 'b':
colorRGB[2] = Serial.read();
blnFade = 0;
break;
case 'c':
Serial.flush();
blnFade = 0;
break;
case 'f':
delayVal = Serial.read();
Serial.flush();
colorFade();
blnFade = 1;
}
}
}

Where it is looking for a "mode" and then runs a function afterwards that may or may not use the second value (it runs serial.flush() when it doesn't need the second character).

There is some more data available at the following links and I'll be working on it this week to make a mind-controlled AR Drone or RC Car for the Atlanta Science Festival next weekend. I may even get to the point where I can make the controls that supplement the NeuroSky run through a Leap Motion if I have time.

http://playground.arduino.cc/interfacing/python#.Uy4SaPldXSA
http://www.instructables.com/id/Arduino-and-Python/?ALLSTEPS
http://forum.arduino.cc/index.php/topic,8332.0.html

Soon, we're gonna have a pretty awesome platform!

Freeside Braniacs

2014-04-06T21:47:17Z

Steamboat: Created page with "Brainiacs is a meetup that is all about Neuroscience and Brain-Computer Interfaces. The first round of projects that we've been working on center around setting up interfaces..."

Brainiacs is a meetup that is all about Neuroscience and Brain-Computer Interfaces.

The first round of projects that we've been working on center around setting up interfaces between different BCI and biometric devices with Python so that it will be much easier to build systems and collect data.

== NeuroSky to Python Interface ==

One of the major points of discussion in the last meeting was how to identify and solve for the individual interfaces to collect biometric data and then push it to other systems like databases or arduinos to act on the data. Here is my walkthrough for the interface between the NeuroSky and Python.

If you're in Windows and haven't fooled around with Python yet and would like a soft introduction, here is my recommendation. This is what I use because I have to do this stuff on my work computer too so it's just easier to manage everything in Windows 7 for me. If you're in Linux then this stuff is way easier for you and you'll probably be using a toolkit of choice there anyway.

1 - Install pythonxy. This is an excellent package for Python in Windows that includes most of the important scientific computing libraries all at once, as well as pip and easy_install (package managers) and iPython Notebook (which is what I use). It also has pandas, opencv, scikits-learn, simpy, and of course numpy and scipy. Apparently it has the necessary tools to build a gui too, but I haven't gotten that far yet.

Uninstall whatever python stuff you have on your computer before installing this so you don't end up with multiple weird instances.

2 - Press windows_key+r to bring up the run dialogue. Type cmd to bring up the command prompt.

3 - Learn how to use the console. You could go through the trouble of learning powershell or using cygwin if you want, but I only use the command prompt to launch ipython and easy_install anyway. I'd rather invest my spare time learning bash, though I'm still pretty terrible at it.

4 - type ipython notebook in whatever folder you want to store your code.

5 - It will bring up your default browser and you can write your code in "cells" that execute individually on a specific kernel for each tab or "notebook." It's really easy.

6 - In the console, type easy_install neuropy and it will pull down the library and set it up for you.

7 - The documentation for the NeuroPy library is pretty easy to read and enough to get you started.

Now, even if you don't have a NeuroSky, you can start to build programs to simulate the generation of the data and what to do with it so that when we hook up the device, we'll just be able to plug in and go. I've tested it with my NeuroSky and was able to replicate the functionality show in the documentation I linked to above.

The python library is much easier to connect to the NS than the phone or tablet apps, which I've found excruciatingly frustrating.

== Python to Arduino Interface ==

Here is some info that I dug up about getting an arduino to talk to python and vice-versa.

For my solution, it worked to send data in two-byte packages. So python basically sends a header and then a 0-255 value with something like:

import serial
port = 'COM6'
baudrate = 9600
arduino = serial.Serial(port, baudrate)

val1 = 255
arduino.write('h' + chr(int(val1)))

...so that the arduino grabs the data like this:

void setup() {
Serial.begin(9600);
}

void loop() {
if(Serial.available() >= 2){
switch( byte( Serial.read() )) {
case 'r':
colorRGB[0] = Serial.read();
blnFade = 0;
break;
case 'g':
colorRGB[1] = Serial.read();
blnFade = 0;
break;
case 'b':
colorRGB[2] = Serial.read();
blnFade = 0;
break;
case 'c':
Serial.flush();
blnFade = 0;
break;
case 'f':
delayVal = Serial.read();
Serial.flush();
colorFade();
blnFade = 1;
}
}

Where it is looking for a "mode" and then runs a function afterwards that may or may not use the second value (it runs serial.flush() when it doesn't need the second character).

There is some more data available at the following links and I'll be working on it this week to make a mind-controlled AR Drone or RC Car for the Atlanta Science Festival next weekend. I may even get to the point where I can make the controls that supplement the NeuroSky run through a Leap Motion if I have time.

http://playground.arduino.cc/interfacing/python#.Uy4SaPldXSA
http://www.instructables.com/id/Arduino-and-Python/?ALLSTEPS
http://forum.arduino.cc/index.php/topic,8332.0.html

Soon, we're gonna have a pretty awesome platform!

Events

2014-04-06T21:29:21Z

Steamboat:

At Freeside Atlanta, we have recurring monthly events where members get together to work on projects, engage in discussions, or just blow off some steam and socialize.

* [[Open House]] (Second and Fourth Tuesdays)

Come out to check out what's going on at Freeside and meet some folks from the local community of hobbyists, artists, researchers, and crazy people!

* [[Analog Game Night]] (First Thursdays)

At Analog Game Night, we get together to play board games and hang out. And also maybe to use the Laser Cutter and 3D Printers to design our own!

* [[TED Talks and Discussion]] (First Wednesday)

Let's get together to watch a few talks and have some discussion! We'll also give some talks of our own, too.

* [[CryptoParty]] (Third Thursday)

CryptoParty is an informal, non-commercial gathering where folks can discuss select topics in privacy, information security and technology.

* [[Freeside Stargazers]] (Third Friday)

A casual astronomy meetup to talk about stars and planets and build our own telescope!

* [[Freeside Braniacs]] (Last Sunday)

Brainiacs is a meetup that is all about neuroscience and brain-computer interfaces.

Events

2014-04-06T21:28:31Z

Steamboat:

At Freeside Atlanta, we have recurring monthly events where members get together to work on projects, engage in discussions, or just blow off some steam and socialize.

* [[Open House]] (Second and Fourth Tuesdays)

Come out to check out what's going on at Freeside and meet some folks from the local community of hobbyists, artists, researchers, and crazy people!

* [[Analog Game Night]] (First Thursdays)

At Analog Game Night, we get together to play board games and hang out. And also maybe to use the Laser Cutter and 3D Printers to design our own!

* [[TED Talks and Discussion]] (First Wednesday)

Let's get together to watch a few talks and have some discussion! We'll also give some talks of our own, too.

* [[CryptoParty]] (Third Thursday)

CryptoParty is an informal, non-commercial gathering where folks can discuss select topics in privacy, information security and technology.

* [[Freeside Stargazers]] (Third Friday)

A casual astronomy meetup to talk about stars and planets and build our own telescope!

* [http://www.meetup.com/Freeside-Atlanta/events/140424412/ Freeside Braniacs] (Last Sunday)

Brainiacs is a meetup that is all about neuroscience and brain-computer interfaces.

Events

2014-04-06T21:28:19Z

Steamboat:

At Freeside Atlanta, we have recurring monthly events where members get together to work on projects, engage in discussions, or just blow off some steam and socialize.

* [[Open House]] (Second and Fourth Tuesdays)

Come out to check out what's going on at Freeside and meet some folks from the local community of hobbyists, artists, researchers, and crazy people!

* [[Analog Game Night]] (First Thursdays)

At Analog Game Night, we get together to play board games and hang out. And also maybe to use the Laser Cutter and 3D Printers to design our own!

* [[TED Talks and Discussion]] (First Wednesday)

Let's get together to watch a few talks and have some discussion! We'll also give some talks of our own, too.

* [[CryptoParty]] (Third Thursday)

CryptoParty is an informal, non-commercial gathering where folks can discuss select topics in privacy, information security and technology.

* [[Freeside Stargazers]] (Third Friday)

A casual astronomy meetup to talk about stars and planets and build our own telescope!

* [http://www.meetup.com/Freeside-Atlanta/events/140424412/ Freeside Braniacs] (Last Sunday)

Brainiacs is a meetup that is all about neuroscience and brain-computer interfaces.

Events

2014-04-06T21:28:02Z

Steamboat:

At Freeside Atlanta, we have recurring monthly events where members get together to work on projects, engage in discussions, or just blow off some steam and socialize.

* [[Open House]] (Second and Fourth Tuesdays)

Come out to check out what's going on at Freeside and meet some folks from the local community of hobbyists, artists, researchers, and crazy people!

* [[Analog Game Night]] (First Thursdays)

At Analog Game Night, we get together to play board games and hang out. And also maybe to use the Laser Cutter and 3D Printers to design our own!

* [[TED Talks and Discussion]] (First Wednesday)

Let's get together to watch a few talks and have some discussion! We'll also give some talks of our own, too.

* [[CryptoParty]] (Third Thursday)

CryptoParty is an informal, non-commercial gathering where folks can discuss select topics in privacy, information security and technology.

* [[Freeside Stargazers]] (Third Friday)

A casual astronomy meetup to talk about stars and planets and build our own telescope!

* [http://www.meetup.com/Freeside-Atlanta/events/140424412/ Freeside Braniacs] (Last Sunday)

Brainiacs is a meetup that is all about neuroscience and brain-computer interfaces.

Infinity Portal

2014-04-06T21:17:50Z

Steamboat:

The Infinity Portal is an interactive art project build for [http://alchemyburn.com/ Alchemy].

The concept of the project centers on an infinity mirror, which is an optical effect created by placing a two-way mirror in front of a regular mirror. Any light source between the two mirrors appears to be reflected forever because only some of the light escapes the two-way mirror. The rest is reflected back, so the viewer's eyes sample the internal reflections in the mirror.

The idea for this project is to create a large archway that appears to be a freestanding gateway standing on an altar. People walk up to the gate, triggering a proximity sensor. Once the system detects that a user is present, the LED strips inside the infinity mirror are triggered, giving the appearance of a portal having opened in the gate and extending backwards infinitely.

== Step 1: Prototyping the concept ==
<gallery>
File:InfinityBuild1Pic1.jpg|The mirror side of the prototype enclosure
File:InfinityBuild1Pic2.jpg|Laying the strips in the prototype enclosure
File:InfinityBuild1Pic3.jpg|Testing the LED setup
File:InfinityBuild1Pic4.jpg|Nathan peers into the wormhole
File:InfinityBuild1Pic5.jpg|A portal in the table
</gallery>

The first round of prototyping involved testing the concept, so we built an Infinity Mirror from parts around the shop, a hardware store run, an LED strip, and some mirror tint ordered online.

We posted a write-up of the build on our [http://blog.freesideatlanta.org/2013/07/infinity-mirror-prototype-build.html blog], which was then featured on [http://hackaday.com/2013/07/23/building-a-blinky-infinity-mirror/ Hack A Day].

We had some good finds from the initial prototyping, and found that we can change the apparent depth of the tunnel by changing the brightness of the LEDs or spacing the two mirrors farther apart. We can make the tunnel appear to curve around by tilting the mirrors slightly. By using two of the two-way mirrors, we found that we could project into the back of the enclosure to make a projected image repeat indefinitely.

== Step 2: Prototyping the design ==
<gallery>
File:InfinityBuild2Pic1.jpg|Tam's concept sketch
File:InfinityBuild2Pic2.jpg|The vector model in CamBam
File:InfinityBuild2Pic3.jpg|The CamBam model with cutting paths set
File:InfinityBuild2Pic4.jpg|Front view of the design prototype
File:InfinityBuild2Pic5.jpg|Side view of the design prototype
File:PortalDiagram.JPG|We decided to sandwich the acrylic between an inner and outer frame
</gallery>

Next, we built a prototype that Tam sketched as a conceptual rendering of the final model. To do this, we vector-mapped her sketch, processed it in CamBam, exported the gcode to the laser cutter and cut a prototype out of wood.

We used the two prototypes that we had (conceptual and design) at the Alchemy Art Fundraiser and received the highest funding at that event. We've still got some fundraising to do, but it looks like people are really excited about this concept!

== Step 3: Planning the Build ==

The build will probably be divided into a few different processes that we'll work on independently:
*Building the framework to support the reflective acrylic pieces
*Designing and milling the facade for the front of the archway
*Programming the light controllers with rainbow chase patterns and setting up triggers
*Laser engraving the acrylic accent pieces for the archway
*Building the Altar and testing different setups to support the illusion

== Step 4: Building the framework ==

<gallery>
File:portalBuild01.jpg|We built the inner frames using support brackets and clamps
File:portalBuild02.jpg|A closer view of the support brackets
File:portalBuild03.jpg|Sizing up the frame on the base
File:portalBuild04.jpg|Testing out the inner frame in the outer frame
File:portalBuild05.jpg|This is the assembly jig to allow us to ship the structure flat
File:portalBuild06.jpg|A test fit of the full assembly
File:portalBuild07.jpg|Drilling out the acrylic and support frames for the support dowels
File:portalBuild08.jpg|The (near-) finished structure
File:portalBuild16.jpg|Pulling the protective coating off of the acrylic
</gallery>

Building the framework took about 5 8-hour work sessions. We used the pallet that the acrylic came in on as a base for the framework.

We ordered the 4x8 sheets of acrylic from Reflection Products in Roswell, Ga. Everything else for the frame was custom-built from the local hardware store.

== Step 5: Building the electronics ==

<gallery>
File:portalBuild09.jpg|Prototyping the brains with a teensy 3.0
File:portalBuild10.jpg|Scott made the final-ish prototype on perfboard
File:portalBuild11.jpg|The facade that Tam designed
File:portalBuild12.jpg|Fitting the LED archway to the milled archway
File:portalBuild13.jpg|The LED assembly jig that Scott designed
File:portalBuild14.jpg|Attaching the LEDs in line so the illusion isn't broken
File:portalBuild15.jpg|Firing up the electronics
</gallery>

We built the electronics using a Teensy 3.0 and a buffer chip (to step the 3.3v up to 5v) to push to the LED data line. We used WS2812 LED strips and powered them with a 70a 5v power supply.

== The Final Result ==

<gallery>
File:portalBuild17.jpg|The fully-assembled structure
File:portalBuild18.jpg|The effect looks pretty good even in the light
File:portalBuild19.jpg|Checking out the full effect
File:portalBuild20.jpg|The effect is pretty mind-blowing in the dark!
</gallery>

The final assembly had a few surprises - because of the way they are manufacturing and hung in the portal, the acrylic sheets have a small warp in them that makes the tunnel look like it opens to a huge room. Pushing on the front of the portal causes the tunnel to warp and change, and both sheets of acrylic are two-way so people can push from both sides to change the effect.

Infinity Portal

2014-04-06T21:10:26Z

Steamboat: /* Step 4: Building the framework */

The Infinity Portal is an interactive art project build for [http://alchemyburn.com/ Alchemy].

The concept of the project centers on an infinity mirror, which is an optical effect created by placing a two-way mirror in front of a regular mirror. Any light source between the two mirrors appears to be reflected forever because only some of the light escapes the two-way mirror. The rest is reflected back, so the viewer's eyes sample the internal reflections in the mirror.

The idea for this project is to create a large archway that appears to be a freestanding gateway standing on an altar. People walk up to the gate, triggering a proximity sensor. Once the system detects that a user is present, the LED strips inside the infinity mirror are triggered, giving the appearance of a portal having opened in the gate and extending backwards infinitely.

== Step 1: Prototyping the concept ==
<gallery>
File:InfinityBuild1Pic1.jpg|The mirror side of the prototype enclosure
File:InfinityBuild1Pic2.jpg|Laying the strips in the prototype enclosure
File:InfinityBuild1Pic3.jpg|Testing the LED setup
File:InfinityBuild1Pic4.jpg|Nathan peers into the wormhole
File:InfinityBuild1Pic5.jpg|A portal in the table
</gallery>

The first round of prototyping involved testing the concept, so we built an Infinity Mirror from parts around the shop, a hardware store run, an LED strip, and some mirror tint ordered online.

We posted a write-up of the build on our [http://blog.freesideatlanta.org/2013/07/infinity-mirror-prototype-build.html blog], which was then featured on [http://hackaday.com/2013/07/23/building-a-blinky-infinity-mirror/ Hack A Day].

We had some good finds from the initial prototyping, and found that we can change the apparent depth of the tunnel by changing the brightness of the LEDs or spacing the two mirrors farther apart. We can make the tunnel appear to curve around by tilting the mirrors slightly. By using two of the two-way mirrors, we found that we could project into the back of the enclosure to make a projected image repeat indefinitely.

== Step 2: Prototyping the design ==
<gallery>
File:InfinityBuild2Pic1.jpg|Tam's concept sketch
File:InfinityBuild2Pic2.jpg|The vector model in CamBam
File:InfinityBuild2Pic3.jpg|The CamBam model with cutting paths set
File:InfinityBuild2Pic4.jpg|Front view of the design prototype
File:InfinityBuild2Pic5.jpg|Side view of the design prototype
File:PortalDiagram.JPG|We decided to sandwich the acrylic between an inner and outer frame
</gallery>

Next, we built a prototype that Tam sketched as a conceptual rendering of the final model. To do this, we vector-mapped her sketch, processed it in CamBam, exported the gcode to the laser cutter and cut a prototype out of wood.

We used the two prototypes that we had (conceptual and design) at the Alchemy Art Fundraiser and received the highest funding at that event. We've still got some fundraising to do, but it looks like people are really excited about this concept!

== Step 3: Planning the Build ==

The build will probably be divided into a few different processes that we'll work on independently:
*Building the framework to support the reflective acrylic pieces
*Designing and milling the facade for the front of the archway
*Programming the light controllers with rainbow chase patterns and setting up triggers
*Laser engraving the acrylic accent pieces for the archway
*Building the Altar and testing different setups to support the illusion

== Step 4: Building the framework ==

<gallery>
File:portalBuild01.jpg|We built the inner frames using support brackets and clamps
File:portalBuild02.jpg|A closer view of the support brackets
File:portalBuild03.jpg|Sizing up the frame on the base
File:portalBuild04.jpg|Testing out the inner frame in the outer frame
File:portalBuild05.jpg|This is the assembly jig to allow us to ship the structure flat
File:portalBuild06.jpg|A test fit of the full assembly
File:portalBuild07.jpg|Drilling out the acrylic and support frames for the support dowels
File:portalBuild08.jpg|The (near-) finished structure
File:portalBuild16.jpg|Pulling the protective coating off of the acrylic
</gallery>

Building the framework took about 5 8-hour work sessions. We used the pallet that the acrylic came in on as a base for the framework.

We ordered the 4x8 sheets of acrylic from Reflection Products in Roswell, Ga. Everything else for the frame was custom-built from the local hardware store.

== Step 5: Building the electronics ==

<gallery>
File:portalBuild09.jpg|Prototyping the brains with a teensy 3.0
File:portalBuild10.jpg|Scott made the final-ish prototype on perfboard
File:portalBuild11.jpg|The facade that Tam designed
File:portalBuild12.jpg|Fitting the LED archway to the milled archway
File:portalBuild13.jpg|The LED assembly jig that Scott designed
File:portalBuild14.jpg|Attaching the LEDs in line so the illusion isn't broken
File:portalBuild15.jpg|Firing up the electronics
</gallery>

== The Final Result ==

<gallery>
File:portalBuild17.jpg|The fully-assembled structure
File:portalBuild18.jpg|The effect looks pretty good even in the light
File:portalBuild19.jpg|Checking out the full effect
File:portalBuild20.jpg|The effect is pretty mind-blowing in the dark!
</gallery>

Infinity Portal

2014-04-06T21:04:58Z

Steamboat:

The Infinity Portal is an interactive art project build for [http://alchemyburn.com/ Alchemy].

The concept of the project centers on an infinity mirror, which is an optical effect created by placing a two-way mirror in front of a regular mirror. Any light source between the two mirrors appears to be reflected forever because only some of the light escapes the two-way mirror. The rest is reflected back, so the viewer's eyes sample the internal reflections in the mirror.

The idea for this project is to create a large archway that appears to be a freestanding gateway standing on an altar. People walk up to the gate, triggering a proximity sensor. Once the system detects that a user is present, the LED strips inside the infinity mirror are triggered, giving the appearance of a portal having opened in the gate and extending backwards infinitely.

== Step 1: Prototyping the concept ==
<gallery>
File:InfinityBuild1Pic1.jpg|The mirror side of the prototype enclosure
File:InfinityBuild1Pic2.jpg|Laying the strips in the prototype enclosure
File:InfinityBuild1Pic3.jpg|Testing the LED setup
File:InfinityBuild1Pic4.jpg|Nathan peers into the wormhole
File:InfinityBuild1Pic5.jpg|A portal in the table
</gallery>

The first round of prototyping involved testing the concept, so we built an Infinity Mirror from parts around the shop, a hardware store run, an LED strip, and some mirror tint ordered online.

We posted a write-up of the build on our [http://blog.freesideatlanta.org/2013/07/infinity-mirror-prototype-build.html blog], which was then featured on [http://hackaday.com/2013/07/23/building-a-blinky-infinity-mirror/ Hack A Day].

We had some good finds from the initial prototyping, and found that we can change the apparent depth of the tunnel by changing the brightness of the LEDs or spacing the two mirrors farther apart. We can make the tunnel appear to curve around by tilting the mirrors slightly. By using two of the two-way mirrors, we found that we could project into the back of the enclosure to make a projected image repeat indefinitely.

== Step 2: Prototyping the design ==
<gallery>
File:InfinityBuild2Pic1.jpg|Tam's concept sketch
File:InfinityBuild2Pic2.jpg|The vector model in CamBam
File:InfinityBuild2Pic3.jpg|The CamBam model with cutting paths set
File:InfinityBuild2Pic4.jpg|Front view of the design prototype
File:InfinityBuild2Pic5.jpg|Side view of the design prototype
File:PortalDiagram.JPG|We decided to sandwich the acrylic between an inner and outer frame
</gallery>

Next, we built a prototype that Tam sketched as a conceptual rendering of the final model. To do this, we vector-mapped her sketch, processed it in CamBam, exported the gcode to the laser cutter and cut a prototype out of wood.

We used the two prototypes that we had (conceptual and design) at the Alchemy Art Fundraiser and received the highest funding at that event. We've still got some fundraising to do, but it looks like people are really excited about this concept!

== Step 3: Planning the Build ==

The build will probably be divided into a few different processes that we'll work on independently:
*Building the framework to support the reflective acrylic pieces
*Designing and milling the facade for the front of the archway
*Programming the light controllers with rainbow chase patterns and setting up triggers
*Laser engraving the acrylic accent pieces for the archway
*Building the Altar and testing different setups to support the illusion

== Step 4: Building the framework ==

<gallery>
File:portalBuild01.jpg|We built the inner frames using support brackets and clamps
File:portalBuild02.jpg|A closer view of the support brackets
File:portalBuild03.jpg|Sizing up the frame on the base
File:portalBuild04.jpg|Testing out the inner frame in the outer frame
File:portalBuild05.jpg|This is the assembly jig to allow us to ship the structure flat
File:portalBuild06.jpg|A test fit of the full assembly
File:portalBuild07.jpg|Drilling out the acrylic and support frames for the support dowels
File:portalBuild08.jpg|The (near-) finished structure
File:portalBuild16.jpg|Pulling the protective coating off of the acrylic
</gallery>

== Step 5: Building the electronics ==

<gallery>
File:portalBuild09.jpg|Prototyping the brains with a teensy 3.0
File:portalBuild10.jpg|Scott made the final-ish prototype on perfboard
File:portalBuild11.jpg|The facade that Tam designed
File:portalBuild12.jpg|Fitting the LED archway to the milled archway
File:portalBuild13.jpg|The LED assembly jig that Scott designed
File:portalBuild14.jpg|Attaching the LEDs in line so the illusion isn't broken
File:portalBuild15.jpg|Firing up the electronics
</gallery>

== The Final Result ==

<gallery>
File:portalBuild17.jpg|The fully-assembled structure
File:portalBuild18.jpg|The effect looks pretty good even in the light
File:portalBuild19.jpg|Checking out the full effect
File:portalBuild20.jpg|The effect is pretty mind-blowing in the dark!
</gallery>

File:PortalDiagram.JPG

2014-04-06T20:43:02Z

Steamboat: A sketch of the infinity portal framework.

A sketch of the infinity portal framework.

File:PortalBuild20.jpg

2014-04-06T20:40:31Z

Steamboat: The effect with the lights out.

The effect with the lights out.

File:PortalBuild19.jpg

2014-04-06T20:39:30Z

Steamboat:

File:PortalBuild18.jpg

2014-04-06T20:38:26Z

Steamboat: The effect is pretty clear even in a well-lit room.

The effect is pretty clear even in a well-lit room.

File:PortalBuild17.jpg

2014-04-06T20:37:14Z

Steamboat: A Walter appears.

A Walter appears.

File:PortalBuild16.jpg

2014-04-06T20:36:07Z

Steamboat: Pulling the protective film off of the acrylic.

Pulling the protective film off of the acrylic.

File:PortalBuild15.jpg

2014-04-06T20:34:51Z

Steamboat: Testing the electronics after assembling the LED and power supply sections.

Testing the electronics after assembling the LED and power supply sections.

File:PortalBuild14.jpg

2014-04-06T20:33:20Z

Steamboat: The assembly jig keeps the LEDs spaced out correctly to keep from breaking the illusion.

The assembly jig keeps the LEDs spaced out correctly to keep from breaking the illusion.

File:PortalBuild13.jpg

2014-04-06T20:31:40Z

Steamboat: Scott's 3D printed LED assembly jig.

Scott's 3D printed LED assembly jig.

File:PortalBuild12.jpg

2014-04-06T20:30:35Z

Steamboat: Fitting the archway for the LEDs based on the arc of the facade.

Fitting the archway for the LEDs based on the arc of the facade.

File:PortalBuild11.jpg

2014-04-06T20:29:14Z

Steamboat: The fascade that Tam designed being fitted on the front.

The fascade that Tam designed being fitted on the front.

File:PortalBuild10.jpg

2014-04-06T20:27:59Z

Steamboat: Steamboat uploaded a new version of "File:PortalBuild10.jpg"

The circuitry using a teensy 3.0 and a buffer chip.

File:PortalBuild10.jpg

2014-04-06T20:27:20Z

Steamboat: The circuitry using a teensy 3.0 and a buffer chip.

The circuitry using a teensy 3.0 and a buffer chip.

File:PortalBuild09.jpg

2014-04-06T20:25:01Z

Steamboat: Prototyping the electronics.

Prototyping the electronics.

File:PortalBuild08.jpg

2014-04-06T20:23:51Z

Steamboat: The support structure of the portal looks kinda like a gallows actually...

The support structure of the portal looks kinda like a gallows actually...

File:PortalBuild07.jpg

2014-04-06T20:22:04Z

Steamboat: Drilling out the acrylic and frames to hold the support dowels.

Drilling out the acrylic and frames to hold the support dowels.

File:PortalBuild06.jpg

2014-04-06T20:19:23Z

Steamboat: Testing the fit of the acrylic, inner, and outer frame.

Testing the fit of the acrylic, inner, and outer frame.

File:PortalBuild05.jpg

2014-04-06T20:18:01Z

Steamboat: Detail shot of the assembly jig.

Detail shot of the assembly jig.

File:PortalBuild04.jpg

2014-04-06T20:16:36Z

Steamboat: Testing the fit of the inner frame.

Testing the fit of the inner frame.

File:PortalBuild03.jpg

2014-04-06T20:15:02Z

Steamboat: Building the supports for the pallet assembly jig.

Building the supports for the pallet assembly jig.

File:PortalBuild02.jpg

2014-04-06T20:13:12Z

Steamboat: Braces used on the inner frame.

Braces used on the inner frame.

File:PortalBuild01.jpg

2014-04-06T20:10:27Z

Steamboat: Edward working on the Portal frame.

Edward working on the Portal frame.

Info

2014-04-06T20:06:19Z

Steamboat:

[[File:Justin Leggett poster.jpg|thumb|250px]]
Freeside Atlanta (est. 2009) is a nonprofit work space built entirely by volunteers. We are a community of makers, tinkerers, engineers, programmers, artists, teachers, and lunatics. As a community, we have built out our space with tools and equipment for electronics, 3D printing, woodworking, metalworking, art, design, classes, and events. Everything you see in [[Our Space|our space]] was donated or built by members.

Our members are engaged in amazing [[Projects|projects]] and love to [[Classes|share knowledge]]. We also develop and work with open source and free technology wherever possible, and try to release our creations under variants of the [https://creativecommons.org/licenses Creative Commons license].

You don't have to be a Freeside member to come to our events or take our classes. We encourage you to come out to the '''Tuesday night Open House''' that we have every other week at 7:30pm or to any of the other public [[Classes|classes]] or [[Events|events]] that we have on [http://www.meetup.com/Freeside-Atlanta Meetup]. Come check the place out and see if this is a community that you'd be interested in [[Joining|joining]]!

== Our Mission ==

Freeside Technology Spaces, a non-profit organization, strives to provide a space that inspires collaboration, creativity, teaching, and open projects for the Atlanta community.

Freeside is a member-run, non-profit corporation registered in Georgia. We have submitted an application for 501(c)3 status exempt for education and scientific research purposes. In the meantime, we have fiscal sponsorship to accept tax-deductible [[Donations|donations]].

We are currently incubating [http://www.liberatedtech.org/ Liberated Tech], a non-profit to retrofit older tech for the Atlanta communities in need. We host their events while they work to get a space of their own.

== Our Space ==

We built our space into different areas to consolidate where we work on stuff in the space. You can check out the different areas of our space [[Our_Space | here]]. We are located at:

675 Metropolitan Parkway 
Suite 6066 
Atlanta, GA 30310

There are [[Detailed Directions|detailed directions]] to our space to help you find the place.

== Freeside by the Numbers ==

* 50 [[Members|members]] and [[Joining|growing]]!
* 1,200+ makers served in 2012
* 6,000 square feet
* 22 [[Our_Space|zones]] of awesomeness
* 1 cat puzzle

== Current Projects ==

Interesting [[Projects | projects]] going on at our space:
* A <$2000 [http://blog.freesideatlanta.org/2013/03/super-cheap-and-effective-off-road.html Off Road Wheelchair] art project
* A [http://blog.freesideatlanta.org/2012/04/draft-freesiders-hackers-collaborate-in.html published white paper] for an open collaboration to 3D print CT scans for pre-surgery planning
* An interactive [https://wiki.freesideatlanta.org/fs/Infinity_Portal Infinity Mirror Archway] art project for Alchemy
* [http://www.learntosolder.org/ LearnToSolder.org] - started by a member for last year's Atlanta Mini Maker Faire
* [https://wiki.freesideatlanta.org/fs/Gaze Gaze Tracking in Rookie and Veteran Surgeons] - Another medical collaboration examining how diagnosticians look at x-rays.
* [[Race_Car| Freeside's ChumpCar Race Car]] - Join the team and race to victory!

== Upcoming Events ==

<shtml version="2" hash="077ef96cabd5093bdf6e83e2be757e3c43c5c8b21f7a0d4af15cc4da3b52d604"><iframe src="/static/meetup.html" frameborder=0>

</iframe></shtml>

Gaze

2014-04-06T20:05:14Z

Steamboat:

<gallery>
File:EyeTrackingEx1.JPG|An example result from a veteran of the study.
File:Rookie_1_adj_s12.JPG|An example reading on one of the more difficult slides
File:Rookie_2_adj_s12.JPG|Another example of the study results
File:Labsetup.jpg|The setup of the test system at Dekalb Medical Center
File:RookieCorrected.JPG|A sample from the Rookie set.
File:OGAMASlideshow.jpg|The test setup in OGAMA for arranging images and setting up the test parameters
</gallery>

What would it look like if you could track, record, and analyze the gaze tracking patterns of surgeons as they are diagnosing x-rays? What kinds of differences might emerge with experience and which of those are the good habits vs. bad habits?

== The initial idea ==

The first step in answering this question is to just have a look and see what patterns emerge. So that's what we did. Nick Giovinco and Steven Sutton collaborated on this project to create a dataset of gaze tracking information from a group of surgical residents and a group of surgeons with years of medical experience.

We used [http://www.gazegroup.org/downloads/23-gazetracker ITU Gazetracker] to capture the gaze information and [http://www.ogama.net/ OGAMA] to record and analyze that data. We then put together a setup with a chin rest and webcam at the Dekalb Medical Center.

== The first study ==

After a day of setup and calibration, we had consistent results and a reliable testing procedure. We tried to make the test as comfortable as possible, but the need for side supports to keep the head from tilting relative to the screen (as you would imagine people might do while examining something like an x-ray) made the setup a little bit awkward.

We collected data from more than 35 people, but narrowed the data set to 15 residents and 15 surgeons with more than 7 years of experience.

We are currently analyzing the data and writing up the results. Preliminary results indicate that experienced diagnosticians scan a tighter area of the image and rookies tend to move in a pattern that jumps around quite a bit more than the veterans. The tracking data is being compared to the recorded diagnoses so that we can look for patterns in the grouping of the data.

Gaze

2014-04-06T20:04:15Z

Steamboat:

<gallery>
File:EyeTrackingEx1.JPG|An example result from the study. This happens to be a sample from a Veteran
File:Labsetup.jpg|The setup of the test system at Dekalb Medical Center
File:RookieCorrected.JPG|A sample from the Rookie set.
File:OGAMASlideshow.jpg|The test setup in OGAMA for arranging images and setting up the test parameters
File:Rookie_1_adj_s12.JPG|An example reading on one of the more difficult slides
File:Rookie_2_adj_s12.JPG|Another example of the study results
</gallery>

What would it look like if you could track, record, and analyze the gaze tracking patterns of surgeons as they are diagnosing x-rays? What kinds of differences might emerge with experience and which of those are the good habits vs. bad habits?

== The initial idea ==

The first step in answering this question is to just have a look and see what patterns emerge. So that's what we did. Nick Giovinco and Steven Sutton collaborated on this project to create a dataset of gaze tracking information from a group of surgical residents and a group of surgeons with years of medical experience.

We used [http://www.gazegroup.org/downloads/23-gazetracker ITU Gazetracker] to capture the gaze information and [http://www.ogama.net/ OGAMA] to record and analyze that data. We then put together a setup with a chin rest and webcam at the Dekalb Medical Center.

== The first study ==

After a day of setup and calibration, we had consistent results and a reliable testing procedure. We tried to make the test as comfortable as possible, but the need for side supports to keep the head from tilting relative to the screen (as you would imagine people might do while examining something like an x-ray) made the setup a little bit awkward.

We collected data from more than 35 people, but narrowed the data set to 15 residents and 15 surgeons with more than 7 years of experience.

We are currently analyzing the data and writing up the results. Preliminary results indicate that experienced diagnosticians scan a tighter area of the image and rookies tend to move in a pattern that jumps around quite a bit more than the veterans. The tracking data is being compared to the recorded diagnoses so that we can look for patterns in the grouping of the data.