{"comment":{"url":"https://api.github.com/repos/FRC4131/FRCStronghold2016/comments/16671806","html_url":"https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16671806","id":16671806,"user":{"login":"Naoki95957","id":9288548,"avatar_url":"https://avatars.githubusercontent.com/u/9288548?v=3","gravatar_id":"","url":"https://api.github.com/users/Naoki95957","html_url":"https://github.com/Naoki95957","followers_url":"https://api.github.com/users/Naoki95957/followers","following_url":"https://api.github.com/users/Naoki95957/following{/other_user}","gists_url":"https://api.github.com/users/Naoki95957/gists{/gist_id}","starred_url":"https://api.github.com/users/Naoki95957/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Naoki95957/subscriptions","organizations_url":"https://api.github.com/users/Naoki95957/orgs","repos_url":"https://api.github.com/users/Naoki95957/repos","events_url":"https://api.github.com/users/Naoki95957/events{/privacy}","received_events_url":"https://api.github.com/users/Naoki95957/received_events","type":"User","site_admin":false},"position":16,"line":15,"path":"src/org/usfirst/frc/team4131/robot/RobotMap.java","commit_id":"b4d50378b9d8f3b15fda17be7cbd010b2b61aeab","created_at":"2016-03-14T03:30:52Z","updated_at":"2016-03-14T03:30:52Z","body":"Arduino\nOn Mar 13, 2016 8:30 PM, \"Naoki95957\" <naoki.l.95957@gmail.com> wrote:\n\n> We discussed it when we first proposed putting an arguing on the bot.\n> Chris said we should look into making a subsystem for sensors,  and if we\n> go this far, pretty lights for the robot\n> On Mar 13, 2016 8:27 PM, \"Ian W\" <notifications@github.com> wrote:\n>\n>> Never heard anything of it.\n>>\n>> The good news is we can put the IMU on a separate branch, which is what\n>> Chris explained to me. We'll basically keep electrical and main code even,\n>> use electrical as a testing platform, and merge any new features from\n>> testing branches into master - same as regular procedure.\n>>\n>> On Sun, Mar 13, 2016 at 8:24 PM, Naoki <notifications@github.com> wrote:\n>>\n>> > Well that's the deal breaker XD. I thought we were going to write some\n>> sort\n>> > of utilities or sensors subsystem.\n>> >\n>> > On Mar 13, 2016 8:21 PM, \"Ian W\" <notifications@github.com> wrote:\n>> >\n>> > > The problem is that the IMU, being in the TankDrive subsystem, does\n>> not\n>> > > care about whether your configuration says you're electrical bot or\n>> not.\n>> > It\n>> > > could say you're Batman, it's still going to create an IMU in the\n>> > TankDrive\n>> > > class, and if that IMU isn't fully implemented, that IMU is going to\n>> be\n>> > > running on competition bot, practice bot, and electrical bot,\n>> > > indiscriminate of whether there's an IMU on the bot or not.\n>> > >\n>> > > Also the no-reference thing is wrong on two counts: 1) Java will still\n>> > > create the object, but the garbage collector will come after it later\n>> (so\n>> > > anything in the constructor will still happen); and 2) that applies to\n>> > > objects, not fields. If you create an object and don't put it in a\n>> > > variable, it will get GC'd, but if you have the Robot referencing a\n>> > > TankDrive that references an IMU, that IMU will be alive as long as\n>> the\n>> > > robot is alive (as long as the program runs).\n>> > >\n>> > > On Sun, Mar 13, 2016 at 8:14 PM, Naoki <notifications@github.com>\n>> wrote:\n>> > >\n>> > > > Java doesn't put anything on the stack not referenced so there isnt\n>> a\n>> > > > possible way for the robot to go and try to set up an imu in the\n>> > previous\n>> > > > scenario. The code builds around an integer that determines what\n>> robot\n>> > it\n>> > > > is based on the file found on the Rio. If the file (WHOAMI.txt)\n>> reads\n>> > > > \"ElectricalBot\" that is the only way code on the electrical written\n>> on\n>> > > and\n>> > > > for the electrical bot will be executed.\n>> > > > On Mar 13, 2016 8:05 PM, \"Ian W\" <notifications@github.com> wrote:\n>> > > >\n>> > > > > I don't think I understand what you're getting at. Call on what,\n>> > > separate\n>> > > > > from electrical? And not referenced != nonexistent.\n>> > > > >\n>> > > > > —\n>> > > > > Reply to this email directly or view it on GitHub\n>> > > > > <\n>> > > >\n>> > >\n>> >\n>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16671645\n>> > > > >\n>> > > >\n>> > > > > .\n>> > > > >\n>> > > >\n>> > > > —\n>> > > > Reply to this email directly or view it on GitHub\n>> > > > <\n>> > >\n>> >\n>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16671696\n>> > > >\n>> > > > .\n>> > > >\n>> > >\n>> > > —\n>> > > Reply to this email directly or view it on GitHub\n>> > > <\n>> >\n>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16671739\n>> > >\n>> >\n>> > > .\n>> > >\n>> >\n>> > —\n>> > Reply to this email directly or view it on GitHub\n>> > <\n>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16671768\n>> >\n>> > .\n>> >\n>>\n>> —\n>> Reply to this email directly or view it on GitHub\n>> <https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16671784>\n>> .\n>>\n>\n"}}