Redo controller code for pressure sensing

[dbenamy]

Pressure sensing code is on the latest ceb press on factor e farm but we're not sure if it's been uploaded to git and there may be multiple versions of code floating around.

Figure out what code's in use now, by investigating on the ose wiki and asking the relevant people. Then update what's in github.

[dwiel]

sorry about the close/reopen. I'm glad that it appears this repo is getting used again.

[tobami]

I would like to help tidying up the code. As a first step all "versions of code floating around" could be listed commenting in this issue. Once we know which version is being used we can decide how to update/merge the code.

[dwiel]

The version which is HEAD of master branch here, is the version which has been reliably operating on my machine for a while now. Just as one data point.

[dbenamy]

@dwiel Does your machine/code do pressure sensing to make sure all bricks have uniform pressure rather than uniform size?

[dwiel]

yep, I was the one to first design/implement that feature :)

[dbenamy]

Oh sweet! :-)

Do you know what version of the CEB press that is? I want to tag HEAD with ceb-press-7 or whatever.

[dwiel]

My CEB Press doesn't really have a version number that I am aware of. The steel is version 4, the controller is custom, but it was the controller version that James replicated at FeF for the presses used on the recent microhouse build. You know what version those were considered?

[dbenamy]

That's great to know. We emailed James to ask if there's a version number
for this overall machine. If not, we'll just declare a number that's bigger
than previous ones.

On Thu, Oct 24, 2013 at 4:31 PM, Zach Dwiel notifications@github.comwrote:

My CEB Press doesn't really have a version number that I am aware of. The
steel is version 4, the controller is custom, but it was the controller
version that James replicated at FeF for the presses used on the recent
microhouse build. You know what version those were considered?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-27027142
.

[dwiel]

sounds good

[tobami]

I'd recommend to use as tag "v7.0" instead of something like "ceb-press-7"...

[tobami]

If current master is the best-working version, then we just need to clean up/merge the folder dwielcode/, right?

[dwiel]

I agree on v7.0. I think it makes sense to move stuff from dwielcode/ to / and either remove other stuff, or move it to an old/ or depricated/

[dwiel]

There were some minor changes that were been made in the field at FeF during the microhouse build that I think could be merged back into master here, but should probably be re-factored into .h constants first, rather than replacing one constant with another. Will have to see @james' latest code to see what changes they had to make. I think it was mostly changes to constants, though I do remember a few additional code paths added to deal with the poor tolerances that their machines were constructed under.

[dbenamy]

I like v7.0.

We should delete the old code. That's what revision control is for! :-)

Do one of you want to take ownership of this ticket?

[dorkmo]

i vote for saving old code. put it up in the attic.
On Oct 24, 2013 3:56 PM, "Daniel Benamy" notifications@github.com wrote:

I like v7.0.

We should delete the old code. That's what revision control is for! :-)

Do one of you want to take ownership of this ticket?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-27029120
.

[dwiel]

maybe we can tag where we are now, and then 'get rid of' old stuff. The whole point of using something like github is that nothing is every actually lost. I agree with @dbenamy

[dbenamy]

Exactly. The old code is always accessible in history, very easily if we
tag the revision before deleting. Keeping junk code around adds friction to
working with the code: it's a little more stuff for a new contributor to
have to process, searching through the code base with grep or similar may
find junk, and eventually you wind up with a mess.

On Thu, Oct 24, 2013 at 9:10 PM, Zach Dwiel notifications@github.comwrote:

maybe we can tag where we are now, and then 'get rid of' old stuff. The
whole point of using something like github is that nothing is every
actually lost. I agree with @dbenamy https://github.com/dbenamy

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-27047914
.

[dorkmo]

sweet! im a github noob. could we directly link to the github history on
the wiki? for in a little explainer about the change from hall effects to
pressure.
On Oct 25, 2013 6:32 AM, "Daniel Benamy" notifications@github.com wrote:

Exactly. The old code is always accessible in history, very easily if we
tag the revision before deleting. Keeping junk code around adds friction
to
working with the code: it's a little more stuff for a new contributor to
have to process, searching through the code base with grep or similar may
find junk, and eventually you wind up with a mess.

On Thu, Oct 24, 2013 at 9:10 PM, Zach Dwiel notifications@github.comwrote:

maybe we can tag where we are now, and then 'get rid of' old stuff. The
whole point of using something like github is that nothing is every
actually lost. I agree with @dbenamy https://github.com/dbenamy

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-27047914>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-27061136
.

[tobami]

OK. I just tagged v7.0 by creating a release:
https://github.com/OSE/ceb-controller/releases

For reference, in the future even "noobs" 😄 can release the current master by going to that URL and clicking on "Draft new release". That will also create a git tag. The "release notes" will be whatever you put in the description of the release. That also gives us packages so the whole repo can be downloaded with a click. Does it look good to you?

I will close this issue then.

[dbenamy]

@tobami:

I like that you went ahead and did this :-)

Based on what I've been able to find out, the current brick press is likely some combination of v2, v3, and v4 so it's sort of a mess. Do you feel like adding a note to the ceb press section on the wiki saying that that tag is in use on various real world brick presses?

@dorkmo, you can see the history by clicking the "commits" button (it goes to https://github.com/OSE/ceb-controller/commits/master). From there you can view the code as it existed at any revision. It's not a bad idea to add some info on how to use git and github to the wiki, or maybe even better, to link to an existing one. I'd suggest putting it in a generic place rather than in one specific machine, since it'll be used for many of them.

[dbenamy]

@tobami I'm updating the ceb press wiki pages based on some new info I got so I'll add references to the right github releases.

[tobami]

@dbenamy yeah, I thought that if you don't like something I did, I can still easily fix the commit/tag 😄

[tobami]

What pages did you update so far? Should I still add a note as you suggest? In any case we could add a link to the wiki in the readme.

[dbenamy]

I overhauled the whole CEB Press area on the wiki. If you go to
http://opensourceecology.org/wiki/CEB_Press, then v4, then research and
development, there's a link to the v4 release on github.

I also updated the link to the code on
http://opensourceecology.org/wiki/CEB_Press_Control_Code which v3 links to.

That's everything I saw that needed updating. If you know of anything I
missed, have at it!

On Sat, Oct 26, 2013 at 1:02 PM, Miquel Torres notifications@github.comwrote:

What pages did you update so far? Should I still add a note as you
suggest? In any case we could add a link to the wiki in the readme.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-27150487
.

[dbenamy]

Oh, the project has a website link in place (top of
https://github.com/OSE/ceb-controller), but it doesn't point to the OSE
wiki. Do you think we should change that?

On Sat, Oct 26, 2013 at 1:02 PM, Miquel Torres notifications@github.comwrote:

What pages did you update so far? Should I still add a note as you
suggest? In any case we could add a link to the wiki in the readme.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-27150487
.

[dbenamy]

It turns out that old link was to a domain that went away. I updated the link to point to the wiki.

[tobami]

OK, I updated the github project description. Everthing looks good now.

[dwiel]

sorry for resurrecting this thread, but it appears that the wrong set of
code was kept in the cleanup/merge. The old code that as far as I know,
no-one is using any more and hasn't been updated in years was kept, and the
version that OSE, James Slade and I were all using was removed (dwielcode).
Anyone mind if I resurrect that and make it master?

I've gotten emails from multiple people asking how get their machine code
set up, which is how I realized all of this. I would love to resolve this
soon if nobody objects.

zach

On Sun, Oct 27, 2013 at 4:03 PM, Miquel Torres notifications@github.comwrote:

OK, I updated the github project description. Everthing looks good now.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-27177848
.

[queglay]

I agree that the github code should ideally reflect the current version
that is on the OSE brick press, It otherwise wouldn't doesn't make sense to
have code on there if OSE isn't running it. I've added James in on this
conversation too zach.

Andrew Graham

http://www.vimeo.com/houdinifx/showreel

On Sun, Apr 27, 2014 at 9:28 AM, Zach Dwiel notifications@github.comwrote:

sorry for resurrecting this thread, but it appears that the wrong set of
code was kept in the cleanup/merge. The old code that as far as I know,
no-one is using any more and hasn't been updated in years was kept, and
the
version that OSE, James Slade and I were all using was removed
(dwielcode).
Anyone mind if I resurrect that and make it master?

I've gotten emails from multiple people asking how get their machine code
set up, which is how I realized all of this. I would love to resolve this
soon if nobody objects.

zach

On Sun, Oct 27, 2013 at 4:03 PM, Miquel Torres notifications@github.comwrote:

OK, I updated the github project description. Everthing looks good now.

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-27177848>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-41498034
.

[dwiel]

ok cool. I've replied to an old thread that was the discussion around the
repo cleanup that caused this problem in hopes of determining if this was
intentional (and if so, why) or accidental.

On Sun, Apr 27, 2014 at 10:31 AM, queglay notifications@github.com wrote:

I agree that the github code should ideally reflect the current version
that is on the OSE brick press, It otherwise wouldn't doesn't make sense
to
have code on there if OSE isn't running it. I've added James in on this
conversation too zach.

Andrew Graham

http://www.vimeo.com/houdinifx/showreel

On Sun, Apr 27, 2014 at 9:28 AM, Zach Dwiel notifications@github.comwrote:

sorry for resurrecting this thread, but it appears that the wrong set of
code was kept in the cleanup/merge. The old code that as far as I know,
no-one is using any more and hasn't been updated in years was kept, and
the
version that OSE, James Slade and I were all using was removed
(dwielcode).
Anyone mind if I resurrect that and make it master?

I've gotten emails from multiple people asking how get their machine
code
set up, which is how I realized all of this. I would love to resolve
this
soon if nobody objects.

zach

On Sun, Oct 27, 2013 at 4:03 PM, Miquel Torres notifications@github.comwrote:

OK, I updated the github project description. Everthing looks good
now.

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-27177848>
.

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-41498034>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-41498105
.

[queglay]

I have a copy of the code OSE is using on the wiki. We are still using it
with minor tweaks specific to each machine. This is all Zach's code from
last year, do let me know if you guys need a link.

-James
On Apr 27, 2014 9:31 AM, "Andrew Graham" queglay@gmail.com wrote:

I agree that the github code should ideally reflect the current version
that is on the OSE brick press, It otherwise wouldn't doesn't make sense to
have code on there if OSE isn't running it. I've added James in on this
conversation too zach.

Andrew Graham

http://www.vimeo.com/houdinifx/showreel

On Sun, Apr 27, 2014 at 9:28 AM, Zach Dwiel notifications@github.comwrote:

sorry for resurrecting this thread, but it appears that the wrong set of
code was kept in the cleanup/merge. The old code that as far as I know,
no-one is using any more and hasn't been updated in years was kept, and
the
version that OSE, James Slade and I were all using was removed
(dwielcode).
Anyone mind if I resurrect that and make it master?

I've gotten emails from multiple people asking how get their machine code
set up, which is how I realized all of this. I would love to resolve this
soon if nobody objects.

zach

On Sun, Oct 27, 2013 at 4:03 PM, Miquel Torres notifications@github.comwrote:

OK, I updated the github project description. Everthing looks good now.

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-27177848>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-41498034
.

[dwiel]

ok cool, thanks James. It sounds like the code in this repo is the wrong
version then. The code that was removed (
1dda075)
was all of my code in dwielcode. The code that was kept hasn't been used
for years. I'll re-clean up so its actually on the latest.

On Sun, Apr 27, 2014 at 10:35 AM, queglay notifications@github.com wrote:

I have a copy of the code OSE is using on the wiki. We are still using it
with minor tweaks specific to each machine. This is all Zach's code from
last year, do let me know if you guys need a link.

-James
On Apr 27, 2014 9:31 AM, "Andrew Graham" queglay@gmail.com wrote:

I agree that the github code should ideally reflect the current version
that is on the OSE brick press, It otherwise wouldn't doesn't make sense
to
have code on there if OSE isn't running it. I've added James in on this
conversation too zach.

Andrew Graham

http://www.vimeo.com/houdinifx/showreel

On Sun, Apr 27, 2014 at 9:28 AM, Zach Dwiel notifications@github.comwrote:

sorry for resurrecting this thread, but it appears that the wrong set
of
code was kept in the cleanup/merge. The old code that as far as I know,
no-one is using any more and hasn't been updated in years was kept, and
the
version that OSE, James Slade and I were all using was removed
(dwielcode).
Anyone mind if I resurrect that and make it master?

I've gotten emails from multiple people asking how get their machine
code
set up, which is how I realized all of this. I would love to resolve
this
soon if nobody objects.

zach

On Sun, Oct 27, 2013 at 4:03 PM, Miquel Torres <
notifications@github.com>wrote:

OK, I updated the github project description. Everthing looks good
now.

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-27177848>
.

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-41498034>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-41498196
.

[dbenamy]

Yeah, you should totally put whatever's actually in use into master.

We should also recreate the v3 and/or v4 releases as needed if it's not too much work: https://github.com/OSE/ceb-controller/releases. If it is too complicated, let's at least delete the wrong release(s).

[dwiel]

I've at least now got master on the right version.

On Sun, Apr 27, 2014 at 3:17 PM, Daniel Benamy notifications@github.comwrote:

Yeah, you should totally put whatever's actually in use into master.

We should also recreate the v3 and/or v4 releases as needed if it's not
too much work: https://github.com/OSE/ceb-controller/releases. If it is
too complicated, let's at least delete the wrong release(s).

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-41505946
.

[dbenamy]

Nice!

Is there any reason to build a custom board for this rather than using an arduino?

[dwiel]

At one point OSE (and I) wanted a custom board so that it could be made
efficiently and cheaply. In my current version I use off the shelf
components arranged in this schematic:

http://upverter.com/zdwiel/2d958299ddd5a35c/CEB-Press-Controller-Board-Schematic/

This schematic doesn't require any custom boards. James, do you know if
there is any documentation for the latest controller board design? I don't
think I ever documented it very well, other than the above schematic, but
maybe there is something else somewhere ... any ideas?

zach

On Sun, Apr 27, 2014 at 3:21 PM, Daniel Benamy notifications@github.comwrote:

Nice!

Is there any reason to build a custom board for this rather than using an
arduino?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-41506044
.

[dwiel]

Here's what I have for the build:
https://docs.google.com/drawings/d/1AxeT5boHsEPlywFx8O94khOHOpDnSFwuXK3kAgsHP1c/edit

You can also see more info here:
http://opensourceecology.org/wiki/James_Slade_Log

I would really suggest using much higher grade buttons and toggles. The
ones we were using were budget and not long term solutions. The rheostats
could probably be improved as well.

On Sun, Apr 27, 2014 at 2:28 PM, Zach Dwiel zdwiel@gmail.com wrote:

At one point OSE (and I) wanted a custom board so that it could be made
efficiently and cheaply. In my current version I use off the shelf
components arranged in this schematic:

http://upverter.com/zdwiel/2d958299ddd5a35c/CEB-Press-Controller-Board-Schematic/

This schematic doesn't require any custom boards. James, do you know if
there is any documentation for the latest controller board design? I don't
think I ever documented it very well, other than the above schematic, but
maybe there is something else somewhere ... any ideas?

zach

On Sun, Apr 27, 2014 at 3:21 PM, Daniel Benamy notifications@github.comwrote:

Nice!

Is there any reason to build a custom board for this rather than using an
arduino?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-41506044
.

[dwiel]

Nice, thanks

On Sun, Apr 27, 2014 at 5:31 PM, James Slade jameswslade@gmail.com wrote:

Here's what I have for the build:

https://docs.google.com/drawings/d/1AxeT5boHsEPlywFx8O94khOHOpDnSFwuXK3kAgsHP1c/edit

You can also see more info here:
http://opensourceecology.org/wiki/James_Slade_Log

I would really suggest using much higher grade buttons and toggles. The
ones we were using were budget and not long term solutions. The rheostats
could probably be improved as well.

On Sun, Apr 27, 2014 at 2:28 PM, Zach Dwiel zdwiel@gmail.com wrote:

At one point OSE (and I) wanted a custom board so that it could be made
efficiently and cheaply. In my current version I use off the shelf
components arranged in this schematic:

http://upverter.com/zdwiel/2d958299ddd5a35c/CEB-Press-Controller-Board-Schematic/

This schematic doesn't require any custom boards. James, do you know if
there is any documentation for the latest controller board design? I don't
think I ever documented it very well, other than the above schematic, but
maybe there is something else somewhere ... any ideas?

zach

On Sun, Apr 27, 2014 at 3:21 PM, Daniel Benamy notifications@github.comwrote:

Nice!

Is there any reason to build a custom board for this rather than using
an arduino?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-41506044
.

[dbenamy]

@dwiel I wasn't on that email thread you replied to. Mind adding me?

@queglay If master is right now, we should delete any copies of the code in the wiki and point everything at github so everyone's on the same page. That sound ok with you?

I'm guessing the release tags are wrong which is going to confuse people trying to build this. In fact, I'm not even sure the concept of which machine is what version are clear :-) I think I better just delete the tags and releases and we'll try to get it right for the future.

I emailed James when I was trying to straighten out the various versions on the wiki, but he didn't have a chance to reply. It's a shame because the mess on the wiki means far fewer people can benefit from all this awesome work.

If it'd help, I'd be willing to hop on a quick phone call with anyone who can fill in some gaps in my knowledge, learn what's what, and then update the wiki a bit.

[dwiel]

The code that is used in the most recent set of CEB Presses @ FeF use
slightly modified versions of the code that is now at master (each machine
requires slightly different versions due to differences in the machines,
though only slight). I agree that the wiki shouldn't be used to store
code, thats the whole point of this repo.

zach

On Sun, Apr 27, 2014 at 8:42 PM, Daniel Benamy notifications@github.comwrote:

@dwiel https://github.com/dwiel I wasn't on that email thread you
replied to. Mind adding me?

@queglay https://github.com/queglay If master is right now, we should
delete any copies of the code in the wiki and point everything at github so
everyone's on the same page. That sound ok with you?

I'm guessing the release tags are wrong which is going to confuse people
trying to build this. In fact, I'm not even sure the concept of which
machine is what version are clear :-) I think I better just delete the tags
and releases and we'll try to get it right for the future.

I emailed James when I was trying to straighten out the various versions
on the wiki, but he didn't have a chance to reply. It's a shame because the
mess on the wiki means far fewer people can benefit from all this awesome
work.

If it'd help, I'd be willing to hop on a quick phone call with anyone who
can fill in some gaps in my knowledge, learn what's what, and then update
the wiki a bit.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-41515010
.

[queglay]

Are we all in agreement that the latest code and starting point is the code
from James? If so, James, send a link.

MJ

On Sun, Apr 27, 2014 at 9:35 AM, James Slade jameswslade@gmail.com wrote:

I have a copy of the code OSE is using on the wiki. We are still using it
with minor tweaks specific to each machine. This is all Zach's code from
last year, do let me know if you guys need a link.

-James
On Apr 27, 2014 9:31 AM, "Andrew Graham" queglay@gmail.com wrote:

I agree that the github code should ideally reflect the current version
that is on the OSE brick press, It otherwise wouldn't doesn't make sense to
have code on there if OSE isn't running it. I've added James in on this
conversation too zach.

Andrew Graham

http://www.vimeo.com/houdinifx/showreel

On Sun, Apr 27, 2014 at 9:28 AM, Zach Dwiel notifications@github.comwrote:

sorry for resurrecting this thread, but it appears that the wrong set of
code was kept in the cleanup/merge. The old code that as far as I know,
no-one is using any more and hasn't been updated in years was kept, and
the
version that OSE, James Slade and I were all using was removed
(dwielcode).
Anyone mind if I resurrect that and make it master?

I've gotten emails from multiple people asking how get their machine
code
set up, which is how I realized all of this. I would love to resolve
this
soon if nobody objects.

zach

On Sun, Oct 27, 2013 at 4:03 PM, Miquel Torres notifications@github.comwrote:

OK, I updated the github project description. Everthing looks good
now.

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-27177848>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-41498034
.

Get Involved: Would you spare me 5 minutes, print out this
flyerhttp://bit.ly/1qeu332for our summer internships of Extreme
Design/Build - and post it around
coffeehouses/university halls near you? See Summer.
Get Involved in Design Sprints: fill out our Team Culturing
Surveyhttp://opensourceecology.org/wiki/Tech_Team_Culturing_Survey,
and we will email you for ad-hoc Design Sprint technical development
sessions.

Marcin Jakubowski, Executive Director
Open Source Ecology
http://opensourceecology.org
+1.816.846.0736

[dwiel]

James got his code from me, and the code that I gave him is what is now
master in this repo. There are slight alterations floating around that
were made for the different machines due to their own quirks, but this
master is correct.

On Wed, May 7, 2014 at 5:51 PM, queglay notifications@github.com wrote:

Are we all in agreement that the latest code and starting point is the
code
from James? If so, James, send a link.

MJ

On Sun, Apr 27, 2014 at 9:35 AM, James Slade jameswslade@gmail.com
wrote:

I have a copy of the code OSE is using on the wiki. We are still using
it
with minor tweaks specific to each machine. This is all Zach's code from
last year, do let me know if you guys need a link.

-James
On Apr 27, 2014 9:31 AM, "Andrew Graham" queglay@gmail.com wrote:

I agree that the github code should ideally reflect the current version
that is on the OSE brick press, It otherwise wouldn't doesn't make
sense to
have code on there if OSE isn't running it. I've added James in on this
conversation too zach.

Andrew Graham

http://www.vimeo.com/houdinifx/showreel

On Sun, Apr 27, 2014 at 9:28 AM, Zach Dwiel notifications@github.comwrote:

sorry for resurrecting this thread, but it appears that the wrong set
of
code was kept in the cleanup/merge. The old code that as far as I
know,
no-one is using any more and hasn't been updated in years was kept,
and
the
version that OSE, James Slade and I were all using was removed
(dwielcode).
Anyone mind if I resurrect that and make it master?

I've gotten emails from multiple people asking how get their machine
code
set up, which is how I realized all of this. I would love to resolve
this
soon if nobody objects.

zach

On Sun, Oct 27, 2013 at 4:03 PM, Miquel Torres <
notifications@github.com>wrote:

OK, I updated the github project description. Everthing looks good
now.

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-27177848>
.

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-41498034>
.

Get Involved: Would you spare me 5 minutes, print out this
flyerhttp://bit.ly/1qeu332for our summer internships of Extreme
Design/Build - and post it around
coffeehouses/university halls near you? See Summer.
Get Involved in Design Sprints: fill out our Team Culturing
Surveyhttp://opensourceecology.org/wiki/Tech_Team_Culturing_Survey,
and we will email you for ad-hoc Design Sprint technical development
sessions.

Marcin Jakubowski, Executive Director
Open Source Ecology
http://opensourceecology.org
+1.816.846.0736

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-42488119
.

[queglay]

Agreed from my understanding
On 07/05/2014 2:57 pm, "Zach Dwiel" notifications@github.com wrote:

James got his code from me, and the code that I gave him is what is now
master in this repo. There are slight alterations floating around that
were made for the different machines due to their own quirks, but this
master is correct.

On Wed, May 7, 2014 at 5:51 PM, queglay notifications@github.com wrote:

Are we all in agreement that the latest code and starting point is the
code
from James? If so, James, send a link.

MJ

On Sun, Apr 27, 2014 at 9:35 AM, James Slade jameswslade@gmail.com
wrote:

I have a copy of the code OSE is using on the wiki. We are still using
it
with minor tweaks specific to each machine. This is all Zach's code
from
last year, do let me know if you guys need a link.

-James
On Apr 27, 2014 9:31 AM, "Andrew Graham" queglay@gmail.com wrote:

I agree that the github code should ideally reflect the current
version
that is on the OSE brick press, It otherwise wouldn't doesn't make
sense to
have code on there if OSE isn't running it. I've added James in on
this
conversation too zach.

Andrew Graham

http://www.vimeo.com/houdinifx/showreel

On Sun, Apr 27, 2014 at 9:28 AM, Zach Dwiel notifications@github.comwrote:

sorry for resurrecting this thread, but it appears that the wrong
set
of
code was kept in the cleanup/merge. The old code that as far as I
know,
no-one is using any more and hasn't been updated in years was kept,
and
the
version that OSE, James Slade and I were all using was removed
(dwielcode).
Anyone mind if I resurrect that and make it master?

I've gotten emails from multiple people asking how get their machine
code
set up, which is how I realized all of this. I would love to resolve
this
soon if nobody objects.

zach

On Sun, Oct 27, 2013 at 4:03 PM, Miquel Torres <
notifications@github.com>wrote:

OK, I updated the github project description. Everthing looks good
now.

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-27177848>

.

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-41498034>
.

Get Involved: Would you spare me 5 minutes, print out this
flyerhttp://bit.ly/1qeu332for our summer internships of Extreme
Design/Build - and post it around
coffeehouses/university halls near you? See Summer.
Get Involved in Design Sprints: fill out our Team Culturing
Surveyhttp://opensourceecology.org/wiki/Tech_Team_Culturing_Survey,
and we will email you for ad-hoc Design Sprint technical development
sessions.

Marcin Jakubowski, Executive Director
Open Source Ecology
http://opensourceecology.org
+1.816.846.0736

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-42488119>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-42488746
.

[queglay]

http://opensourceecology.org/wiki/File:CEB_code.rar

That's the version I was using with minor tweaks specific to each machine.
On May 7, 2014 4:51 PM, "Marcin Jakubowski" marcin@opensourceecology.org
wrote:

Are we all in agreement that the latest code and starting point is the
code from James? If so, James, send a link.

MJ

On Sun, Apr 27, 2014 at 9:35 AM, James Slade jameswslade@gmail.comwrote:

I have a copy of the code OSE is using on the wiki. We are still using it
with minor tweaks specific to each machine. This is all Zach's code from
last year, do let me know if you guys need a link.

-James
On Apr 27, 2014 9:31 AM, "Andrew Graham" queglay@gmail.com wrote:

I agree that the github code should ideally reflect the current version
that is on the OSE brick press, It otherwise wouldn't doesn't make sense to
have code on there if OSE isn't running it. I've added James in on this
conversation too zach.

Andrew Graham

http://www.vimeo.com/houdinifx/showreel

On Sun, Apr 27, 2014 at 9:28 AM, Zach Dwiel notifications@github.comwrote:

sorry for resurrecting this thread, but it appears that the wrong set
of
code was kept in the cleanup/merge. The old code that as far as I know,
no-one is using any more and hasn't been updated in years was kept, and
the
version that OSE, James Slade and I were all using was removed
(dwielcode).
Anyone mind if I resurrect that and make it master?

I've gotten emails from multiple people asking how get their machine
code
set up, which is how I realized all of this. I would love to resolve
this
soon if nobody objects.

zach

On Sun, Oct 27, 2013 at 4:03 PM, Miquel Torres <
notifications@github.com>wrote:

OK, I updated the github project description. Everthing looks good
now.

—
Reply to this email directly or view it on GitHub<
https://github.com/OSE/ceb-controller/issues/2#issuecomment-27177848>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-41498034
.

Get Involved: Would you spare me 5 minutes, print out this flyerhttp://bit.ly/1qeu332for our summer internships of Extreme Design/Build - and post it around
coffeehouses/university halls near you? See Summer.
Get Involved in Design Sprints: fill out our Team Culturing Surveyhttp://opensourceecology.org/wiki/Tech_Team_Culturing_Survey,
and we will email you for ad-hoc Design Sprint technical development
sessions.

Marcin Jakubowski, Executive Director
Open Source Ecology
http://opensourceecology.org
+1.816.846.0736

[dbenamy]

I changed everything on the wiki that used to point to http://opensourceecology.org/wiki/File:CEB_code.rar, to instead point to the github repo. I also added a giant warning to that file page to come here instead :-)

Hopefully this'll prevent future confusion with what version is the latest and where people should work.

If anyone who wants to work on this isn't comfortable with git and github, I'd be happy to help you/them get up and running.