User Tools

Site Tools


haas:fall2019:data:projects:dsi0

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
haas:fall2019:data:projects:dsi0 [2018/08/20 11:36] – external edit 127.0.0.1haas:fall2019:data:projects:dsi0 [2019/08/18 12:15] (current) – [Submit Tool Usage] wedge
Line 34: Line 34:
 **NOTE:** Week 1 journal entry will be due before Thursday of week2, the remainder of the intro Journal content will be due by this project's deadline. **NOTE:** Week 1 journal entry will be due before Thursday of week2, the remainder of the intro Journal content will be due by this project's deadline.
  
-====Mailing List==== 
-Using the resources found on the course homepage (or the lab46 website in general), locate and subscribe a preferred and frequently checked e-mail address to the class mailing list (known as **DATA**). 
  
-We will use this for class discussions (along with irc, the notes wiki page, your Journal, etc.) and to disseminate announcements and other information. 
- 
-Once subscribed, please send a message to the list introducing yourself (also so I can know to associate a particular e-mail address with you). 
- 
-If you have any preferred nickname, please mention it. And also specify your current program/major of study (helps to get a feel for how the class is constructed). 
 ====Class Chat (IRC)==== ====Class Chat (IRC)====
-Using the [[/haas/fall2018/common/class_chat|tutorial]], set up a screen session and join the **#csci** channel on irc. This has proven useful for more interactive (debugging!) conversations.+Using the [[/haas/fall2019/common/class_chat|tutorial]], set up a screen session and join the **#csci** channel on irc. This has proven useful for more interactive (debugging!) conversations.
  
 Additionally, the C/C++ Programming students will be on this channel, so you could further review your C skills by helping them out. Additionally, the C/C++ Programming students will be on this channel, so you could further review your C skills by helping them out.
Line 58: Line 51:
  
 ====Personal/Per-User Lab46 Mercurial Repository==== ====Personal/Per-User Lab46 Mercurial Repository====
-To both aid you and help you develop better development skills, I'd like for you to make regular commits and pushes to your [[/haas/fall2018/common/repo|Lab46 mercurial repository]].+To both aid you and help you develop better development skills, I'd like for you to make regular commits and pushes to your [[/haas/fall2019/common/repo|Lab46 mercurial repository]].
  
 This way, you can have a regular snapshot of your work as you go along, plus have the ability to grab an older copy should something go wrong. This way, you can have a regular snapshot of your work as you go along, plus have the ability to grab an older copy should something go wrong.
Line 72: Line 65:
     * Late submissions will lose 25% credit per day, with the submission window closing on the 4th day following the deadline.     * Late submissions will lose 25% credit per day, with the submission window closing on the 4th day following the deadline.
   * Run the **submit** tool by the deadline to record your completion.   * Run the **submit** tool by the deadline to record your completion.
 +
 +=====Submission Criteria=====
 +To be successful in this project, the following criteria must be met:
 +
 +  * Project must be submit on time, by the posted deadline to be eligible for full credit.
 +    * Late submissions will lose 25% credit per day, with the submission window closing on the 4th day following the deadline.
 +    * Early submissions can earn 1 bonus point per day in advance of the posted due date.
 +  * All code must compile cleanly (no warnings or errors)
 +    * all requested functions must be implemented in the related library or program
 +    * all requested functionality must conform to stated requirements (either on this project page or in comment banner in source code files themselves).
 +  * Executed programs must display in a manner similar to provided output
 +    * output formatted, where applicable, must match that of project requirements
 +  * Processing must be correct based on input given and output requested
 +  * Output, if applicable, must be correct based on values input
 +  * Code must be nicely and consistently indented (you may use the **indent** tool)
 +  * Code must be commented
 +    * Any "to be implemented" comments **MUST** be removed
 +      * these "to be implemented" comments, if still present at evaluation time, will result in points being deducted.
 +    * Sufficient comments explaining the point of provided logic **MUST** be present
 +  * Track/version the source code in a repository
 +  * Submit a copy of your source code to me using the **submit** tool by the deadline.
 +  * Make sure your submitted source code is in a file called **hello.c**
 +  * Make sure it outputs exactly like the sample output above.
 +  * Create and submit a text file called **info.text** that contains the following information:
 +    * preferred name/nickname
 +    * preferred non-lab46 e-mail address
 +    * program you are matriculated in
 +    * irc nick used in class chat (your username if unchanged)
 +    * other information I should know
  
 ====Submit Tool Usage==== ====Submit Tool Usage====
Line 77: Line 99:
  
 <cli> <cli>
-lab46:~/src/data/dsi0$ submit data dsi0+lab46:~/src/data/dsi0$ submit data dsi0 info.text
 Submitting data project "dsi0": Submitting data project "dsi0":
 +    -> info.text(OK)
  
 SUCCESSFULLY SUBMITTED SUCCESSFULLY SUBMITTED
Line 84: Line 107:
 </cli> </cli>
  
 +I'll be evaluating the project based on the following criteria:
 +
 +<code>
 +39:dsi0:final tally of results (39/39)
 +*:dsi0:customized journal title [5/5]
 +*:dsi0:customized journal intro [6/6]
 +*:dsi0:joined class irc chat [4/4]
 +*:dsi0:submitted info.text file [4/4]
 +*:dsi0:provided requested information in info.text [8/8]
 +*:dsi0:cloned lab46 mercurial repository into ~/src [4/4]
 +*:dsi0:committed and pushed populated .hgignore file [4/4]
 +*:dsi0:configured hgrc file [4/4]
 +</code>
 +
 +Additionally:
 +  * Solutions not abiding by spirit of project will be subject to a 25% overall deduction
 +  * Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
 +  * Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction
 +  * Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction
haas/fall2019/data/projects/dsi0.1534779408.txt.gz · Last modified: 2018/08/20 11:36 by 127.0.0.1