Perl 6 - the future is here, just unevenly distributed

IRC log for #webwork, 2014-02-14

| Channels | #webwork index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:10 mgage joined #webwork
01:38 mgage joined #webwork
03:30 mgage joined #webwork
04:36 mgage joined #webwork
05:19 rbeezer joined #webwork
11:42 mgage joined #webwork
15:41 shdw_work joined #webwork
15:45 aubreyja joined #webwork
15:45 aubreyja joined #webwork
17:58 shdw_work for someone who has never done object-oriented programming before, its real entertaining trying to figure out how to add a new module :-)
18:08 rbeezer joined #webwork
18:57 goehle joined #webwork
21:54 ionparticle joined #webwork
21:56 ionparticle goehle, thanks for the response. Question: If a user problem doesn't have the '
21:56 goehle the ' ?
21:56 ionparticle 'needs_grading' or the 'graded' flag
21:56 ionparticle is it safe to assume that it's not an essay question
21:56 ionparticle ?
21:57 goehle as long as the number of attempts is greater than one
21:57 goehle (and assuming that a question wasn't added after they made an attempt)
21:57 goehle so for example if a professor tries a problem
21:57 goehle well yeah
21:57 goehle so that
21:57 goehle in particular if you are thinking of just testing one user
21:57 goehle you cant really test the professor
21:58 goehle because they probably wont have submitted an answer to the problem
21:58 ionparticle yeah, that's what I was thinking
21:58 goehle you could have it start the loop
21:58 goehle and then exit if it finds a user with a nonzero number of attempts an no flags
21:59 goehle the issue is that the system doesnt know there is an essay answer in the problem until someone actually submits something
22:00 ionparticle yeah, so still not a really good solution
22:00 goehle the way I have it now the first time anyone submits an answer to the problem it will set a global flag on the globalProblem object
22:01 goehle that will trigger the link, and you only need to check globalProblem for each problem (not for every user)
22:03 ionparticle wow, that was fast, is it in the repo?
22:04 goehle Its not in the main repo
22:04 goehle but its on my git
22:04 goehle are you running 2.8?
22:05 goehle git checkout -b goehle-essayslow master
22:05 ionparticle yes
22:05 goehle git pull https://github.com/goehle/webwork2.git essayslow
22:05 goehle if so
22:05 goehle then those two commands will create a new branch on your server
22:05 goehle and pull my changes into it
22:05 goehle if you want to get back to the way it was before, just git checkout master
22:08 ionparticle I did try optimizing the database access by taking them out of the loop
22:08 goehle that probably helped a little, but ultimately the tiny bit of information provided by the link wasn't work the computation time
22:08 goehle at least imo
22:08 ionparticle but it didn't really help much since the amount of database accesses is still alot
22:08 ionparticle yeah
22:09 goehle thats going to be a lot of students to grade if you do have an essay problem
22:09 goehle I suppose you wont be doing those, though
22:10 ionparticle haha, funnily enough, I was asked to take a look at MIT's machine grading stuff recently
22:10 ionparticle but no, these courses don't have essay problems
22:11 goehle well if this fix doesnt work
22:11 goehle (it should but if it doesnt) then you could just disable that part of the code
22:11 goehle not super elegant but it will solve your problem
22:11 ionparticle well, it doesn't help for the mock course I set up
22:11 ionparticle cause it's got no attempts
22:11 ionparticle lol
22:12 goehle :D
22:12 goehle does the mock course have lots and lots of students?
22:12 goehle that could still be used to test it, even with no attempts
22:12 ionparticle yeah, 3000
22:12 goehle since the old version was checking every userProblem entry, irregardless of number of attempts
22:13 goehle could you zip that up and send it to me somehow
22:13 goehle that would be useful to have for testing
22:13 ionparticle sure
22:22 goehle so did that help?  I have to go soonish and wanted to see if there was anything else that needs to be done
22:22 goehle (I try not to break webwork at big institutions, so I want to get this tested right away if I can)
22:25 ionparticle sorry, got pulled away for another thing
22:25 goehle oh no worries
22:26 ionparticle no worries, I'm testing this in the dev server
22:26 ionparticle doesn't matter if it breaks
22:26 goehle a smart choice
22:26 ionparticle I'll leave a message here or on the newsgroup when it's done
22:27 goehle sounds good
22:28 goehle left #webwork
22:38 goehle joined #webwork

| Channels | #webwork index | Today | | Search | Google Search | Plain-Text | summary