help2002 articles all ANNOUNCEMENTS recent articles
login to post a new article
tagged articles (914 / 1171) the unit in general (21) lectures (4) workshops (4) labs (25) final exam (105) 1st project (323) seeking a 1st project partner (62) 2nd project (255) seeking a 2nd project partner (58) systems in the news (7) just interesting (33) software hacks (3) computer-systems history (14)
help2002 topics from today and yesterday from the past week from the past two weeks ALL topics, most recent first
  login
chapter0 unitinfo research projects
csforum csse-feedback csbreakdown cssubmit csmarks
1st semester help fora Computer Networks Data Structures and Algorithms Graphics and Animation Mobile and Wireless Computing Object Oriented Programming Open Source Tools and Scripting Software Requirements and Design Software Testing and Quality Assurance
  It's UWAweek 30 (2nd semester, week 1)

help2002

This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.
Displaying selected article
Showing 1 of 1168 articles.
Currently 7 other people reading this forum.
 UWA week 36 (2nd semester, mid-semester break) ↓
SVG not supported

Login to reply

👍?
helpful
5:08pm Mon 4th Sep, Christopher M.

ANONYMOUS wrote:
> If our measurements are to match with the output of the sample solution in order to get full marks for the automated marking, some confirmation about the sample solution would be great. At the moment, i'm adding 1 usec (in my solution) before a system call happens in order to get the same measurements as the sample solution, but it feels very wrong to do so.
I'm unsure if this is a new point, or if you're reiterating the same point made in your post just 77 minutes earlier?

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G 		Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  7:24AM Jul 25 2024
Privacy policy