14:18 < sam_moore> http://git.ucc.asn.au/?p=matches/MCTX3420.git;a=summary
14:19 < Callum__> yea agreed
14:19 < Callum__> and that is kinda weird
+14:20 < Callum__> i cant seem to find anything in account settings for a timezone
+14:21 < Callum__> Anything else we need done by tomorrow? because i have a bunch of other stuff I'd like to get done
+14:21 < sam_moore> While you're in account settings, you can set your author name for commits
+14:22 < sam_moore> No, there's nothing urgent at this stage
+14:22 < sam_moore> It's only the first week, and we only need 1 page
+14:22 < sam_moore> We can be like "Here is a page of details on how we got Git to work" if we have to
+14:22 < Callum__> Yea just we need to make sure we have enough for 1 page
+14:23 < Callum__> hmm, true i suppose. set up IRC + git repo + discussed an outline on what is going to be required
+14:24 < Callum__> Tbh he'l likely be happy if we just give him a summary of those meeting minutes
+14:25 < Callum__> Anyway i'l divert my attention for now then. If you come across anything interesting or something that can be done il stick around in the channel
+14:25 < sam_moore> Ok, thanks
+14:26 < sam_moore> The first automatic commit of the irc logs seems to have worked!
+14:26 < sam_moore> It also copies everything to git.ucc so we have a backup
+14:26 < Callum__> nice
+14:27 < sam_moore> The times might be correct as well :P
+14:27 < Callum__> was just like "where is it? " then i realise i was looking at my forked repo
+14:27 < sam_moore> Oh, just make sure you don't push anything to the git.ucc repo, because it doesn't go the other way
+14:27 < sam_moore> Actuall I'll just remove everyone's keys to stop that from happening
+14:28 < Callum__> haha, good to be sure. We need to make sure the other 2 have this sorted out. hopefully they rock up to the meeting tomorrow
+14:28 < Callum__> oh wow. the logs go all the way back to when you first connected
+14:28 < Callum__> haha
+14:30 < Callum__> and according to me the logs were commited 15 hours ago
+14:32 < sam_moore> Yeah, my logs will be the best to keep because I don't have to quit, so I should get everything
+14:33 < Callum__> yea
+14:34 < Callum__> Sigh. end of first week. already just written myself a fairly long list of things i need to do, which is by no means comprehensive
+14:36 < sam_moore> I think I have a lot of work to do as well, I should do something for another unit
+14:36 < sam_moore> See you later
+14:36 < Callum__> later
+15:32 < sam_moore> Ok, so pretty much anyone can comment on our stuff, and pretty much anyone can submit bug reports
+15:32 < sam_moore> I'm going to say that's useful, and we should tell all the other teams about it
+15:33 < sam_moore> Also I was supposed to go do something else, whoops
+18:35 < sam_moore> I changed my username because someone pointed out it sounds like "matches succ"
+18:35 < sam_moore> But the old links should redirect
+18:36 -!- justin_ is now known as justin_kruger
+18:37 < sam_moore> Whoops
+20:21 < Callum__> whoops?
+21:20 < sam_moore> EOF From client
+21:32 < sam_moore> I wonder how I can get people's forks to merge into the main repository without them having to issue a pull request
+21:34 < sam_moore> Ah, I can't, because basically they have total control over their own fork
+21:35 < sam_moore> Everyone just remember to fetch from upstream before you do work and issue a pull request when you are done, and hopefully things will stay relatively in sync.
+--- Day changed Mon Aug 05 2013
+00:00 -!- Irssi: #mctxuwa_softdev: Total of 1 nicks [0 ops, 0 halfops, 0 voices, 1 normal]
+10:33 -!- Callum_ [
[email protected]] has quit ["AndroIRC - Android IRC Client ( http://www.androirc.com )"]
+11:19 < Callum> hallo
+11:29 < sam_moore> Hi
+11:30 < sam_moore> I've spoken to Omid from the electronics team, they are in charge of the "microcontroller"
+11:31 < sam_moore> Apparently they think a raspberry pi is a good choice
+11:31 < sam_moore> I told him we thought we might need a lower level device to do the ADC/DAC in particular
+11:32 < sam_moore> But they seem to think a raspberry pi by itself will work
+11:33 < sam_moore> I'm kind of not sure who's responsible for this part, since we have "server hardware" and they have "microcontroller" and the raspberry pi is sort of both
+11:33 < sam_moore> But if we agree we want a raspberry pi it probably won't be an issue
+11:33 < sam_moore> Also apparently the unit coordinators recommended the raspberry pi as well
+11:34 < Callum> Yea he did
+11:34 < james__> Well we are using the raspberry pi as a server
+11:34 < james__> And we can bootstrap microcontrollers onto it
+11:34 < james__> So i guess we are in charge of the pi
+11:35 < james__> And the are in charge of the hardware around it
+11:35 < james__> *they
+11:35 < sam_moore> Seems logical
+11:36 < sam_moore> I don't know if you get email notifications; I did a block diagram using the ideas from our first meeting
+11:36 < sam_moore> I kind of added some thoughts of my own
+11:38 < sam_moore> Hopefully it makes sense
+11:41 < sam_moore> If either of you gets time, would you like to start typing some of the progress report?
+11:51 < james__> Do we have to submit a progress report? Because the guide to mechatronics project work that was on lms said we had to do some things for week 1 but not that
+11:52 < sam_moore> I'm pretty sure we do
+11:52 < sam_moore> Hang on
+11:53 < sam_moore> All teams are expected to report next monday (see the report format in the unit outline/overview).
+11:53 < sam_moore> All teams must review their sub-system and provide high level detail of what is required.
+11:54 < sam_moore> All team must take an integrated approach. (I assume this means we have to start talking to other teams ASAP)
+11:54 < sam_moore> I think the block diagram is a good start for the high level detail
+11:54 < sam_moore> Then make some notes about how we're collaborating using git
+11:55 < james__> git and irc
+11:55 < sam_moore> We should decide whether Rowan or I will be the meeting convener
+11:56 < james__> I think you
+11:56 < james__> Just because you actually know what is going on
+11:56 < sam_moore> Yes, I'm happy to do it and I think I can do a good job
+11:56 < sam_moore> I just don't want to try and take over the group or something
+11:56 < sam_moore> I have a good idea of what's going on, but we'll still need everyone to contribute
+11:57 < sam_moore> I'm not a particular expert in any area, I just sort of know enough to have a general idea of how to approach things
+11:57 < james__> Its important that the person who represents us has a firm knowledge base of whats possible and what we plan to do. Ultimately you are the person who best fills those requirements
+11:58 < sam_moore> Ok, thanks, if everyone agrees we'll tell Rowan that when we meet
+11:58 < sam_moore> And he can still talk to his friends for us, in fact the more of us that can communicate with the other teams the better
+11:59 < james__> True
+12:00 < james__> there isn't anything that says he can't talk to others
+12:00 < sam_moore> Omid said his team was going to rotate the meeting convener, maybe we could try that later on once everyone has a better idea of what we're doing
+12:00 < sam_moore> Anyway, I should do some other work, see you at 2pm
+12:01 < james__> Yeah might be worth it. Gives everyone a taster
+12:01 < james__> okay see you then
+20:38 < sam_moore> I'm going to try using the GitHub issues and milestones thing
+20:39 < sam_moore> It might help with keeping track of what we need to do and what we've done
+20:50 < sam_moore> I think we had some difficulty setting specific goals for this week
+20:50 < sam_moore> I can try and put together some longer term goals as a start, if that's helpful
+20:51 < sam_moore> Hmm
+20:52 < sam_moore> We weren't given a lot of requirements that the guy was asking us about
+21:06 < sam_moore> So the most important task seems to be "determine those requirements"
+21:07 < sam_moore> Well, we talked about it in the meeting, but I'm going to make GitHub issues for each of the areas so we have a good record
+21:32 < Callum__> Sam are you talking to yourself or am i not just seeing the other messages?
+21:35 < sam_moore> Yeah, just ranting
+21:36 < sam_moore> Well if you read the messages, then I was talking to you :P
+21:37 < Callum__> haha just they seemed like they were structured like you were responding to someone
+21:39 < sam_moore> I guess that's how I'm used to using IRC, people tend to say stuff broadly directed at anyone even though they won't get an immediate reply
+21:39 < sam_moore> Or even if they don't need a reply
+21:45 < Callum__> Fair enough
+--- Day changed Tue Aug 06 2013
+15:12 < Callum__> Is the only image processing that needs doing detecting the edge of the can? (and doing measuring how it changes with time etc)
+15:39 < Callum__> hey
+15:39 < james__> what up
+15:39 < sam_moore> Hi
+15:39 < Callum__> Is the only image processing that needs doing detecting the edge of the can? (and doing measuring how it changes with time etc)
+15:40 < sam_moore> Callum__: I think so
+15:40 < james__> As far as i understand it yes
+15:40 < Callum__> plus just booted up ubuntu on laptop. havent touched it since i did C programming a year ago xD
+15:40 < sam_moore> It would also be nice to just have unprocessed images streamed to the GUI
+15:40 < Callum__> yea what i was thinking
+15:41 < Callum__> firstly, i can look into only processing a portion of the image, so we could get away with a larger resolution
+15:41 < sam_moore> With the server side interface, I'm starting to think I'll ditch the apache2 webserver + CGI and integrate a minimal webserver + the lower level stuff into the same program
+15:41 < Callum__> and openCV has a couple of algorithms to detect edges
+15:41 < Callum__> so will likely look into one or 2 of those
+15:41 < sam_moore> Just thinking about all the layers that are involved with the CGI approach... it probably won't turn out easier to code, and it will definitely be slower
+15:42 < sam_moore> Plus, if we really care about performance, the apache2 webserver has a lot of features we don't care about
+15:42 < james__> As long as i can access the raw files etc i should be able to display it via a gui
+15:42 < sam_moore> The main one being it's designed to cope with multiple users well, and we want to configure it to only allow ONE user
+15:43 < sam_moore> Yes, that sounds good
+15:44 < Callum__> responding to who? me or james?
+15:44 < sam_moore> Um... both now
+15:44 < Callum__> haah
+15:45 < sam_moore> Anyway, I've realised that our software will place an upper limit on the quality of the sensors
+15:45 < james__> true
+15:45 < sam_moore> Since we weren't given a requirement on quality, we should aim to get it as high as feasible
+15:45 < sam_moore> But sensors group needs to have some idea of the upper limit that our software will place on quality
+15:45 < Callum__> yea.
+15:46 < james__> Start simple and ramp it up until the hardware breaks?
+15:46 < sam_moore> No point streaming 1000 images a second if the JavaScript GUI can't send requests that fast.
+15:46 < sam_moore> Yep.
+15:46 < sam_moore> I know you're supposed to do task break downs and all that time management stuff, but the fact is we need to experiment with actual code to work out the best implementation
+15:47 < james__> yeah. break it down into code and test code?
+15:48 < sam_moore> Maybe?
+15:49 < sam_moore> Well, we've got a high level idea of the software
+15:49 < sam_moore> The first tasks should be "decide on the best software implementation of each level"
+15:49 < sam_moore> To do that we need to test some minimalistic implementations
+15:50 < Callum__> yea
+15:50 < sam_moore> So, to set a goal for week 2, can it be "Decide on software implementation at each point in the block diagram"
+15:51 < sam_moore> And "Determine upper limit on data transfer rate through software systems"
+15:51 < sam_moore> The second one might take a bit longer.
+15:52 < Callum__> githubs down for maintenance. hahah
+15:52 < sam_moore> That happened like 2 seconds after I submitted a comment on the CGI stuff
+15:53 < sam_moore> For a while it was showing me a Unicorn (?)
+15:53 < Callum__> yea i got that before
+15:53 < Callum__> when trying to access on my laptop
+15:53 < sam_moore> Well... we have the git.ucc server
+15:54 < sam_moore> But I was starting to like the Issues and Comments and all those actual features
+15:54 < Callum__> hmm. doubt it will be down for long. will have to see
+16:10 < Callum__> back up
+18:35 < Rowan> test test
+18:35 < Rowan> ??
+18:43 < Callum__> Hey
+18:56 -github:#mctxuwa_softdev- [MCTX3420] none pushed 2 new commits to master: http://git.io/ZDMvew
+18:56 -github:#mctxuwa_softdev- MCTX3420/master 64b0cd9 Sam Moore: Investigate software for interfacing with hardware via HTTP requests...
+18:56 -github:#mctxuwa_softdev- MCTX3420/master 5afaa23 Sam Moore: Merge branch 'master' of github:szmoore/MCTX3420
+18:57 -github:#mctxuwa_softdev- [MCTX3420] none pushed 1 new commit to master: http://git.io/1nMEMA
+18:57 -github:#mctxuwa_softdev- MCTX3420/master 9579cea Sam Moore: Makefile for webserver test...
+--- Day changed Wed Aug 07 2013
+00:24 -github:#mctxuwa_softdev- [MCTX3420] none pushed 1 new commit to master: http://git.io/5DEPzw
+00:24 -github:#mctxuwa_softdev- MCTX3420/master fe2fc11 Sam Moore: More work on webserver test...
+00:52 -github:#mctxuwa_softdev- [MCTX3420] none pushed 1 new commit to master: http://git.io/r6aFJw
+00:52 -github:#mctxuwa_softdev- MCTX3420/master e615433 Sam Moore: Add necessary HTTP response headers...
git.ucc.asn.au / matches / MCTX3420.git / blobdiff
UCC git Repository :: git.ucc.asn.au