Rensselaer Center for Open Source Software

Mason Cooper

In the past week we have added database bindings to project, as mongo will be our core in terms of data and site management. In the coming days we will be adding our actual build system and prototype admin panel for plug-in control.

Speaking of which, we're heading in a direction where all of our primary systems and functionality will be done through plug-in modules that will be completely customize-able, restricted by a permissions system that the core maintains. Features will be granted permissions in a manner similar to applications on the android operating system, where they can require permissions (along with the ability for optional permissions) and users will be presented with the permission request so they are informed of what systems their plug-ins are trying to access. This will hopefully make Aro an incredibly modular system.

Features that we see essential will be delegated to a core set of plug-ins. The core classification will be reserved for plug-ins that have no other dependencies. In the future we will determine a specification for these along with the plug-ins that will add additional functionality to our CMS.

Oh, also, everything is going to be archery themed. Look for the puns. We could loose one at any time.

Post • Aro CMS • 1 hour ago
2 files changed, 1 line added, 1 line removed
makinj
Commit • MeNext • 2 hours ago
Jake Weiss
2 files changed, 1 line added, 1 line removed

Need to change plan classes and recompile Linux against older versions of glibc post release.

Commit • Milkyway@Home • 3 hours ago
Alex Vargas

I have started code on the Android version of the app. So far there is really only a main page with some buttons and a logger page with some buttons. Nothing is functional yet, and we are just in the starting stages.

Also, we have a separate repository for the android version which can be found here: https://github.com/nachosthatrpink/Spoiler_Android

Post • Spoiler • 17 hours ago
14 files changed, 2044 lines added, 16 lines removed
PeterRyder1
Commit • Check up • 19 hours ago
burke livingston
2 files changed, 3 lines added, 0 lines removed
Commit • Whiteboard • 21 hours ago
burke livingston
10 files changed, 80 lines added, 17 lines removed
Commit • Whiteboard • 21 hours ago
Jazmine Olinger
2 files changed, 32 lines added, 0 lines removed
Commit • Neptune • 23 hours ago
14 files changed, 169 lines added, 69 lines removed
lmoynihan
Commit • LED Color Control • 1 day ago
Brian Kelley
10 files changed, 186 lines added, 81 lines removed

Well, probably. I'll test the tracking later.

Commit • Where R U? • 1 day ago
4 files changed, 42 lines added, 25 lines removed
makinj
Commit • MeNext • 1 day ago
shinya hirata
2 files changed, 145 lines added, 0 lines removed
shinya hirata
2 files changed, 45 lines added, 0 lines removed
shinya hirata
2 files changed, 0 lines added, 45 lines removed
shinya hirata
2 files changed, 45 lines added, 0 lines removed
12 files changed, 311 lines added, 227 lines removed
PeterRyder1
Commit • Check up • 1 day ago
Peter Ryder
26 files changed, 2511 lines added, 544 lines removed

Gui rewrite

Commit • Check up • 1 day ago
4 files changed, 100 lines added, 126 lines removed

Made stuff stable

Sensechen
Commit • RPI Clubs and Activities • 1 day ago
Kevin Zheng
60 files changed, 1060 lines added, 125 lines removed
Commit • Lights Out • 1 day ago
David Kim

By we I mean Dimitar (of course) and me.We are working on Peirce Logic again and it will (hopefully) be our last semester working on it.By this point we have fixed several issues and added some features including:Redundant timeline branch checkingSaving and Loading of proofsUI improvementsTimeline improvementsGeneral Tablet / Mobile tweaksFor Fall 2014, we hope to finally finish up touch support for the app and add a few more quality of life features, such as shortcuts for common Logic Structure...

Post • Peirce-Logic • 1 day ago
Charles Machalow
2 files changed, 1 line added, 1 line removed

fixed incorrect info in comment

Commit • cDashboard • 2 days ago
4 files changed, 60 lines added, 0 lines removed
sarbos
Commit • Neptune • 2 days ago
2 files changed, 1 line added, 1 line removed

rClubs logo in corner now links back to the homesite

Sensechen
Commit • RPI Clubs and Activities • 2 days ago
2 files changed, 1 line added, 1 line removed

Height of page changed

Sensechen
Commit • RPI Clubs and Activities • 2 days ago
4 files changed, 68 lines added, 72 lines removed
  • Fixed Scaling
  • Added some links
  • Hover over links
Sensechen
Commit • RPI Clubs and Activities • 2 days ago
Aaron Cheng
6 files changed, 207 lines added, 99 lines removed
John Drogo
6 files changed, 120 lines added, 2 lines removed

Added mongo bindings and test scripts. Looks like Aro can remember things now. We'll need to add plugin sandboxing at some point but that's a ways off.

Commit • Aro CMS • 2 days ago
6 files changed, 31 lines added, 23 lines removed
makinj
Commit • MeNext • 2 days ago
2 files changed, 3 lines added, 3 lines removed

no more &quot everywhere)

makinj
Commit • MeNext • 2 days ago
2 files changed, 9 lines added, 3 lines removed

R=bruening@google.com BUG=NONE

Review URL: https://codereview.appspot.com/148820043

git-svn-id: http://dynamorio.googlecode.com/svn/trunk@2845 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6

zhaoqin@google.com
Commit • DynamoRIO Projects • 2 days ago
Paul Revere

Just posting our first talk in case anyone is looking for more information on our project

https://docs.google.com/presentation/d/1YNFqln33hZBm5fqVTX1gVrduRTA2snyDgFhABlzQXNw/edit?usp=sharing

-Paul

Post • Vest • 2 days ago
Aaron Gunderson
6 files changed, 10 lines added, 5 lines removed
Commit • Whiteboard • 2 days ago
Justin Etzine
6 files changed, 31 lines added, 23 lines removed
Commit • MeNext • 2 days ago
4 files changed, 28 lines added, 9 lines removed
jaked122
Commit • Command Chain • 2 days ago
4 files changed, 2 lines added, 0 lines removed
PeterRyder
Commit • Check up • 3 days ago
Cyril George
4 files changed, 342 lines added, 0 lines removed
Commit • Plan of Study • 3 days ago
Kevin O'Connor

Despite the lack of commits, I've been hard at work building the foundation for the project. Currently I'm focused on building out the base scrapper that will be used to fetch results and then provide an interface to collect information from.

My main focus right now is setting up a nice configurable worker setup as well as extensionable modeling system. My main goal for this is to make it quick and easy for people to write new modules that can easily be recompiled back into the main framework. In this way all the datasets can be managed as their own open-source projects.

As a part of this goal, my initial setup is being done with scrapping the Laundry Alert service. I figured this would be a sufficient challenge since their HTML is pretty terrible navigate in any intelligible form. My initial commit will likely lack this service, but it will closely follow thereafter.

Post • PuckmanLabs • 3 days ago
4 files changed, 98 lines added, 25 lines removed
joncrall
Commit • IBEIS • 3 days ago

We are starting to make headway with some of the code review that we have been working on for Pokemon RPI. In addition to making a few helper classes more versatile, we have also ironed out a bug in the main game engine that was choking on large map sizes. More updates to come soon.Also here is a map that shows some of the complexity of the program.

Ted Tenedorio
Post • Pokemon RPI • 3 days ago
John Behnke
24 files changed, 240 lines added, 194 lines removed
Commit • Where R U? • 3 days ago
Justin Etzine
2 files changed, 1 line added, 1 line removed
Commit • MeNext • 3 days ago
Justin Etzine
2 files changed, 66 lines added, 39 lines removed
Commit • MeNext • 3 days ago
8 files changed, 98 lines added, 38 lines removed
joncrall
Commit • IBEIS • 3 days ago
Paul Revere
4 files changed, 10 lines added, 14 lines removed
Commit • Vest • 3 days ago
Darren Lin
2 files changed, 1 line added, 3 lines removed
Commit • Emissary • 3 days ago
Darren Lin
2 files changed, 1 line added, 0 lines removed
Commit • Emissary • 3 days ago
Darren Lin
2 files changed, 1 line added, 1 line removed
Commit • Emissary • 3 days ago
Darren Lin
4 files changed, 1 line added, 6 lines removed
Commit • Emissary • 3 days ago
Darren Lin
6 files changed, 3 lines added, 3 lines removed
Commit • Emissary • 3 days ago
Darren Lin
2 files changed, 6 lines added, 1 line removed
Commit • Emissary • 3 days ago
Darren Lin
4 files changed, 6 lines added, 3 lines removed
Commit • Emissary • 3 days ago
Darren Lin
6 files changed, 10 lines added, 6 lines removed
Commit • Emissary • 3 days ago
2 files changed, 58 lines added, 56 lines removed
PeterRyder
Commit • Check up • 3 days ago
Justin Etzine
6 files changed, 5 lines added, 5 lines removed
Commit • MeNext • 3 days ago
Justin Etzine
2 files changed, 1 line added, 1 line removed
Commit • MeNext • 3 days ago
2 files changed, 5 lines added, 2 lines removed
PeterRyder
Commit • Check up • 3 days ago
Aaron Gunderson
150 files changed, 13892 lines added, 4 lines removed
Commit • Whiteboard • 3 days ago
Michael Zemsky
2 files changed, 11 lines added, 1 line removed
Commit • BountyBB • 3 days ago
Michael Zemsky
2 files changed, 35 lines added, 0 lines removed
Commit • BountyBB • 3 days ago
20 files changed, 68 lines added, 33 lines removed

more efficient chipmatch

joncrall
Commit • IBEIS • 4 days ago
Justin Etzine
2 files changed, 1 line added, 1 line removed
Commit • MeNext • 4 days ago
2 files changed, 10 lines added, 3 lines removed
V2870 (Conference ID)
Commit • Milkyway@Home • 4 days ago
8 files changed, 89 lines added, 50 lines removed
joncrall
Commit • IBEIS • 4 days ago
Arya Seghatoleslami

We started this project with pretty high hopes. I, Arya, started on the front end and Tom started looking into the back end. Once the simple stuff was out of the way, I began brushing up on backbone but realized it's not necessary for this app. A minor snafu, but nothing compared to us finding out that the RPI Events page has almost none of the events that offer free food on campus! It was looking bad for a day or two; without a feed to pull events from, YumYum! was screwed. Eventually we thought of pulling the info from emails since this is actually how most events with free food are spread. This will be a tough task for just one developer though and so I have taken on the task of learning Rails to help Tom. Yes I said we were using Node.js before but for now Rails can do the job easily and we may even keep it like this.

Post • YumYum • 4 days ago
Sebastian Sarbora

Hey guys,

Now that the start of school excitement is dying down we are getting into actually working on Neptune. Essentially, the goal for this semester is to have something that can move and see.

Veronica and Dan will be working on designing and creating Motor controller boards for each of the six motors(2 for each axis of movement) as well as power management and batteries.

Charlotte is currently working on sending and receiving data between the main controller and the host computer over HTTP via an ethernet module.

Jazmine will be working on the program that will actually communicate with Neptune, with the main tasks being Interpreting USB gamepad controls and developing the UI.

I will also be working on the program, specifically on interfacing with the webcam, which uses HTTP and streaming mjpeg to send video. I will also work on the main controller for motion control algorithms so that the rover moves smoothly in both translation and rotation, and to possibly have some balance type control.

The hope is to be able to use the gamepad to send commands over to the controller that move the motors while simultaneously receiving video. A secondary goal is to actually test it in the water, assuming we are able to get all of the mechanics of waterproofing and buoyancy worked out by the end of the semester.

Post • Neptune • 4 days ago
Jesse Freitas
8 files changed, 117 lines added, 79 lines removed
Commit • Homework Server • 4 days ago
2 files changed, 6 lines added, 1 line removed

drx-created log files have mixed slashes on Windows - use correct dir-sep in Windows and Unix

R=bruening@google.com BUG=1540

Review URL: https://codereview.appspot.com/147760043

git-svn-id: http://dynamorio.googlecode.com/svn/trunk@2844 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6

zhaoqin@google.com
Commit • DynamoRIO Projects • 4 days ago
6 files changed, 167 lines added, 1 line removed
joncrall
Commit • IBEIS • 5 days ago
Keenan Sanchez

I sent an email to the webmaster of the Delmar-Bethlehem EMS website a few weeks ago and finally got a response yesterday. I said that I wanted to add functionality such that our database could be accessed through their site. Here was Bob's response:

"Hi Keenan,

I apologize it has taken me so long to reply to you regarding this. I think your desire to create a database with images of the EMTs CMEs is commendable. At this time, Delmar-Bethlehem EMS is in a period of transition from our previous administrator to a future named administrator. In addition, we are working to streamline our CME program. I will review your recommendation with our Chief and will contact you once we know the direction we intend to proceed.

Thank you, Bob"

Not exactly a breakthrough but I find feedback like this to be (oddly) motivating. You'd think it'd be more motivating to receive constructive criticism -- something that moves you closer to the finish line.

Post • FireDB • 5 days ago
0 files changed, 0 lines added, 0 lines removed
Shelts
Commit • Milkyway@Home • 5 days ago
0 files changed, 0 lines added, 0 lines removed
Shelts
Commit • Milkyway@Home • 5 days ago
8 files changed, 131 lines added, 7 lines removed
  • run common.fib with drcov
  • use runtest.cmake to invoke drcov2lcov
  • check the final output file

based on patch by dtouch3d: https://codereview.appspot.com/92410046/

R=bruening@google.com BUG=none

Review URL: https://codereview.appspot.com/141160043

git-svn-id: http://dynamorio.googlecode.com/svn/trunk@2839 49cc7528-f6fd-11dd-9d1a-b59b2e1864b6

zhaoqin@google.com
Commit • DynamoRIO Projects • 5 days ago
Tommy Fang

Hey guys, we'll be focusing on code review for about a month or so in order to fix all the bugs and ensure that we are able to deliver beta by the end of the semester. We've organized the code visually and are working hard to fix every single bug. I've also began focusing more on the game concept document ideas. I'll organize this document and make it readable so I can share it with everyone. We'd like to hear some feedback on our project once we get beta rolling, so we can begin the iterative d...

Post • Pokemon RPI • 5 days ago
Brian Kelley
44 files changed, 390 lines added, 99 lines removed
Commit • Where R U? • 5 days ago
Brian Kelley
58 files changed, 591 lines added, 19 lines removed

Next up, I need to get the icons above the tab title text

Commit • Where R U? • 5 days ago
Daniel Lowe

Starting to re-write the interactions with images that are written in matplotlib into Qt to make them cleaner, more responsive and more elegant.

Post • IBEIS • 5 days ago
2 files changed, 0 lines added, 1 line removed
PeterRyder1
Commit • Check up • 5 days ago
10 files changed, 48 lines added, 54 lines removed

but pretty dope right?

makinj
Commit • MeNext • 5 days ago

With a new semester comes more time and resource to work on Docktor, as well as a new set of goals for us to just barely make! Below is the schedule for the next 12 weeks, expect a usable shipped application by the end of it! Week 1-3: Decide on basic UI design and lay out framework for such. Week 4-6: Work with different OS X input packages and find fastest responding framework for using key combos to change docks Week 7-9: Implement custom key combos into the user interface Week 10-12:Touch ...

Theo
Post • Docktor (For OSX) • 5 days ago

Download File

Post • Sheng Guan Tu • 5 days ago
Sebastian Sarbora
2 files changed, 5 lines added, 0 lines removed
Commit • Neptune • 5 days ago
Zachary Minster
26 files changed, 230 lines added, 43 lines removed

Fixed bug involving new version Swift 1.0 and Xcode 6.1. Separated aspects of code into individual functions for fail and success.

Commit • Where R U? • 5 days ago
2 files changed, 1 line added, 0 lines removed
joncrall
Commit • IBEIS • 5 days ago
Alexander White

Sqlite is not a suitable thing for scaling upwards, as I would like it to be, so therefore, we will eventually end up using PostgreSQL which is a much more scalable database with much better security and more extensive features.

Also, our interface is pretty bad, so I'm looking for anything to make the design better.

Post • Command Chain • 5 days ago
Tausif Ahmed

The basic foundation code provided by Xcode for IOS apps has been added to the github repo. The layout of the app will be a tabbed view so that there will be different "pages" for the app and they will be available through a tab menu at the bottom of the app. Currently on the basic code that has been added only has 2 tabs and they both contain empty pages.

Post • Spoiler • 5 days ago
94 files changed, 1214 lines added, 0 lines removed

Added Xcode files for IOS version of Spoiler

emt13
Commit • Spoiler • 5 days ago
Tausif Ahmed
94 files changed, 1214 lines added, 0 lines removed
Commit • Spoiler • 5 days ago
Evan Thompson
90 files changed, 0 lines added, 1183 lines removed
Commit • Spoiler • 5 days ago
4 files changed, 39 lines added, 37 lines removed
Jon Crall <jon.crall@BakerStreet>
Commit • IBEIS • 5 days ago
2 files changed, 30 lines added, 26 lines removed
Jon Crall <jon.crall@BakerStreet>
Commit • IBEIS • 5 days ago
8 files changed, 81 lines added, 14 lines removed
Jason Parham
Commit • IBEIS • 5 days ago

This is the first post for BallotBox, a cross-platform, anonymous voting system. It will be developed for web, iOS, and Android. In the far future, we might also develop an app for Windows Phone.The web app will be written using Ruby on Rails. This is partly due to the fact that Rails makes it incredibly easy to create the initial infrastructure we need for the app, so we can quickly get into the nitty-gritty with algorithm development and server interaction.We haven't made final decisions on th...

XenosInAHat
Post • BallotBox • 5 days ago
Kirk Smith
150 files changed, 996 lines added, 0 lines removed
Commit • BallotBox • 5 days ago
4 files changed, 39 lines added, 37 lines removed
joncrall
Commit • IBEIS • 6 days ago
John Behnke

One of the first issues we came across with designing a multi-platform app was the design.

The basic design for Where R U? calls for a tab-based application with three main views: Map, My Rides, and Settings. The rough UI layout we made had this tab bar at the bottom of the screen. While this works great on iOS, since i-Devices have a physical home button, it does not work as well on newer Android devices that lack physical OS-related buttons such as home, back, and multitask. Instead of physical buttons, they rely on software implementations of the buttons that occupy the bottom of the screen, which is where we had the app's tab bar initially. Another issue caused by the platform's differences is how to navigate tabs. Tabs can be navigated using left-to-right or right-to-left swipes on Android by default; however, iOS relies on actually touching the different tabs and implementing swipe-based tab-switching is not very straight forward.

One of the biggest choices we have to make due to the differences in the platforms is mapping services. Both the iOS and Android versions of the apps can use Google Maps for the mapping services, only iOS can use Apple Maps (for obvious reasons). Initially we decided to use Google Maps for both; however, as more research into the mapping APIs was done, we figured that Apple Maps' API (MapKit) would be far easier to implement on iOS and allow for a more "native" experience with the default Maps application.

Because of these differences, we decided to take the approach of "Do what is best for each platform", rather than trying to make changes to each version of the app that won't fit the platform. While this approach makes sense for simple UI choices, it could cause issues with things like the mapping where GPS directions could differ between mapping services. Unless the mapping services differ by a significant amount in terms of directions or route optimization, we will play to the strengths of the individual platforms.

Post • Where R U? • 6 days ago
Derek Meer

First update in a few weeks. We have been in contact with Thomas Watteyne, the head of the OpenWSN project. He has helped us get started with the code and running simulations. Mike has also purchased a Raspberry PI for the TAP virtual interface. This allows us to run the "simulated" nodes on a separate computer. We spent the past week doing research on the issues and/or projects we'd like to tackle first. Today's meeting will finalize our first assignment. So we're almost started!We also have co...

Post • OpenWSN • 6 days ago
8 files changed, 58 lines added, 40 lines removed
joncrall
Commit • IBEIS • 6 days ago
8 files changed, 249 lines added, 52 lines removed
Sensechen
Commit • RPI Clubs and Activities • 6 days ago

Post • Sheng Guan Tu • 6 days ago
Kevin Zheng

Lights Out is a novel mobile app idea - no published mobile apps currently exist yet that do exactly what I am aiming for the app to do, which is to remind the user to turn off their car lights. Because it’s a first of its kind, it is exciting to work on, but it also means that planning how it will be used and what the specific use cases of the software will be can be a daunting task, as there are no previous examples to work off of.

So far, I have been shaping out the functionality as I code the app - this ensures that I know what Android can and can’t do, so I know what to limit the app’s functionality to. For instance, I found out that Android apps can run services in the background that even run when the phone is asleep. This is very useful, good news as it means that the user does not need to awaken their phone on a road trip for the app to shoot a reminder, as was previously anticipated. However, it raises a big design necessity - minimize battery usage of the app, since it must run at all times, essentially, to be useful. We don’t want the user’s phone to die on the road, before it has the chance to shoot a reminder in the first place.

As I shaped out the app in the process of coding, I carved out basic details on how the app will work. The app itself really doesn’t require much user input; there is a settings page where the user enters in necessary info for the app to work, such as their home location(s) and notification email addresses. Once the user puts in their home location, they then leave the app running in the background. When the GPS detects that the user’s phone has moved a threshold distance away from their home location, and it is currently night hours, it will fire a reminder. The reasoning is that once the user is a certain distance away from their home locations, then they will have had to drive there. (This is the most reliable way I can currently think of to determine when a user needs to turn off their car lights - obviously, it is not foolproof, as for one, they can use public transportation at night - see the proposal blog post for more info on issues and workarounds.) Reminders can be sent to email, or iPhone / Android notifications, or both.

Reminder notifications can work in several ways, based on the user’s style of lifestyle, and patterns of phone / technology use. If they do not check emails often, but check phone notifications often, then the app could send a phone notification the instant it detects when a notification should fire. Then, the user would be alerted; from here, they would open the app, where they can specify when to send another notification (which they will set to the estimated time that they will arrive home). That way, they get another notification right as they leave their cars from home (ideally, although there will likely be some estimation error). If the user checks emails often, then the app could just send an email. Then, when they arrive home, hopefully the first thing in their inbox will be the car light reminder. This will be the case even if they checked their email before arriving home. However, if their inbox gets cluttered quickly, the reminder could be deep into their inbox once they arrive home. In this case, the app could be obnoxious and constantly send emails every M minutes for a time period of N hours once a notification has been determined to be sent. Of course, this would be a configurable setting, and only used for those desperately in need of the strongest reminders that they can get.

There are several features that could be added to Lights Out to provide a better experience. One is to set “exception” timespans where the app will not fire any notifications during that time period. These timespans can be recurring or single-instance. For example, if the user knows that every Thursday evening they carpool off their roommate’s car, they can set a recurring exception from 6:00 PM - 3:00 AM on Thursdays. That way, the user won’t be hit with extraneous notifications in that case, helping minimize false positive reports.

Another feature could be to have the user be able to mark down which notifications that they successfully “did not need” - i.e. an instance where a notification was properly sent, but they did remember to turn off their lights. Also, they could mark down the converse - notifications that they forgot. This marking down helps analyze patterns in the user’s forgetfulness and may aid them in their goal of never forgetting to turn of their car lights.

Finally, the app could have many tweakable settings, such as GPS polling frequency, threshold distance from home location for notifications to fire, whether to use GPS or just Wifi for location detection (Wifi is more inaccurate, but better on battery life), minimum time between notifications, etc.

Post • Lights Out • 6 days ago