[[Category:OPS435-Python]][[Category:ebrauer]]
= Overview : du Improved =Programs such as screenfetch and top are used to generate <code>du</code> is a summary of tool for inspecting directories. It will return the computer's current state. These types contents of programs a directory along with how much drive space they are useful because they present a lot of information quicklyusing. However, and it can be parse its output quickly suggest a possible avenue of investigation for the systems administrator.For this assignment you will create , as it usually returns file sizes as a "System Information" type program. This program will briefly present important information about the state number of the computer system.bytes:
The preliminary <code should look like this:><b>user@host ~ $ du --max-depth 1 /usr/local/lib</b></code>Hostname: NeoMex<pre>164028 /usr/local/lib/herokuKernel Release: 511072 /usr/local/lib/python2.4.0-48-generic7Uptime: up 1 week, 1 day, 17 hours, 14 minutes----------------------------------------92608 /usr/local/lib/node_modules8 /usr/local/lib/dev [ ] 0 %python3.8267720 / [============= ] 65 %usr/bootlocal/efi [==== ] 18 %lib</home [=============== ] 77 %----------------------------------------Mem [======== ] 40 %Swap [= ] 3 %pre>You will therefore be creating a tool called </b>duim (du improved></b>. Your script will call du and return the contents of a specified directory, and generate a bar graph for each subdirectory. The bar graph will represent the drive space as percent of the total drive space for the specified directory.An example of the finished code>your script might produce is this:
In addition<code><b>user@host ~ $ ./duim.py /usr/local/lib</b></code><pre> 61 % [============ ] 160.2 MiB /usr/local/lib/heroku 4 % [= ] 10.8 MiB /usr/local/lib/python2.7 34 % [======= ] 90.4 MiB /usr/local/lib/node_modules 0 % [ ] 8.0 kiB /usr/local/lib/python3.8Total: 261.4 MiB /usr/local/lib</pre> The details of the final output will be up to you, but you will be expected required to build fulfill some specific requirements before completing your script. Read on this capability with some relevant functions. ..
= Assignment Requirements =
== Permitted Modules ==
<b><font color='blue'>Your python script is allowed to import only the <u>os, subprocess and sys</u> modules from the standard library and all the built-in functions.</font></b>
== Required Functions ==
You will need to complete the functions inside the provided file called <bcode>assignment1duim.py</bcode>. The provided <code>checkA1.py</code> will be used to test these functions.
* <code>call_dfcall_du_sub()</code> should take no arguments the target directory as an argument and return a list of strings returned by the shell command<b>du -d 1<target directory></b>.** Use subprocess.Popen. ** '-d 1' specifies a <i>max depth</i> of 1. Your list shouldn't include files, just a list of subdirectories in the target directory.** Your list should <u>not</u> contain newline characters. * <code>call_freepercent_to_graph()</code> should take no two arguments, : percent and the total chars. It should return a list of strings from the shell'bar graph' as a string.* * Your function should check that the percent argument is a valid number between 0 and 100. It should fail if it isn't. You can <code>call_hostname()raise ValueError</code> and in this case.** <b>total chars</b> refers to the total number of characters that the bar graph will be composed of. You can use equal signs <code>call_uptime()=</code> should take no argumentsor any other character that makes sense, but the empty space <b>must be composed of spaces</b>, and should return strings from at least until you have passed the shellfirst milestone.* * The string returned by this function should only be composed of these two characters. For example, calling <code>percent_to_graph(percent50, 10)</code> will take an integer should return: 'percent===== ' and return * <code>create_dir_dict</code> should take a bar graph that represents this percentage. The bar graph should begin with '['list as the argument, and end with ']'. Then contents inside should be 20 characters longreturn a dictionary.* * The list can be the list returned by <code>print_percent_linecall_du_sub(name, percent)</code> is provided . ** The dictionary that you return should have the full directory name as a convenience for you. It will print a properly formatted line<i>key</i>, such and the number of bytes in the directory as the one in <i>value</i>. This value should be an integer. For example, using the example aboveof <b>/usr/local/lib</b>, the function would return: {'/usr/local/lib/heroku': 164028, '/usr/local/lib/python2.7': 11072, ...}
== Additional Functions ==
Your code will need to have some additional functions that will accomplish the following: * The output from <code>call_df()</code> should be filtered to omit any lines that contain <b>loop</b> or <b>tmpfs</b>. These are not proper file systems and should not be displayed.* The output from <code>call_free()</code> should be used to calculate a percent of <b>memory used</b> divided by <b>total memory</b>. * The output from uptime should be in "pretty" format, that is, in weeks, days, and so on. You may create this as a Python functionany other functions that you think appropriate, or especially when you may also want begin to explore another way to do thisbuild additional functionality. Part of your evaluation will be on how "re-usable" your functions are, and sensible use of arguments and return values.
== Use of GitHub ==
You will be graded partly on the quality of your Github commits. You may make as many commits as you wish, it will have no impact on your grade. The only exception to this is <b>assignments with very few commits.</b> These will receive low marks for GitHub use and may be flagged for possible academic integrity violations.<b><font color='blue'>Assignments that do not adhere to these requirements may not be accepted.</font></b>
Professionals generally follow these guidelines:
* commit their code after every significant change,
* the code <i>should hopefully</i> run without errors after each commit, and
* every commit has a descriptive commit message.
After fixing a problem, make a commit and push your code.
<b><u>GitHub is your backup and your proof of work.</bu></ub> These guidelines are not always possible, but you will be expected to follow these guidelines as much as possible. Break your problem into smaller pieces, and work iteratively to solve each small problem. Test your code after each small change you make, and address errors as soon as they arise. It will make your life easier! == Additional Features ==
After completing the aboveThese guidelines are not always possible, but you are will be expected to add some additional (two or more) functions providing useful informationfollow these guidelines as much as possible. Some programs you might want to look at are: * [https://https://ostechnix.com/neofetch-display-linux-systems-information/ screenfetch/neofetch]* [https://htop.dev/ top/htop/Bashtop] It is expected that the additional features you provided should be usefulBreak your problem into smaller pieces, non-trivial, they should not require super-user privileges and should not require the installation of additional modules or packageswork iteratively to solve each small problem.<b>In this part of the assignment, it is better to try for something useful and fail than it is to implement something trivial! I am looking for evidence that Test your code after each small change you have worked with Linux machines and know what kinds of information are useful to see at a glance.</b> You might consider:* Network information/IP addresses* The state of some important daemons/systemd services* process information* information about online users* number of packages installed* cpu load You may even choose to make the output more attractive/colourful etc. If so, you <i>are permitted to use more modules</i> than those specified above, but make sure that the required functions still succeed and address errors as soon as they are. You may want to look into default arguments, ask me for clarification if you're interestedarise.It will make your life easier!
== Coding Standard ==
All your Python code for this assignment must be placed in the provided Python file called <b>assignment1.py</b>. <u>Do not change the name of this file.</u> Please complete the declaration <b><u>as part of the docstring</u></b> in your Python source code file (replace "Student Name" with your own name).
= Submission Guidelines and Process = == The First Milestone (due October 19) ==* Before you begin programming, it is important to plan your algorithm. Therefore your first task will be to complete and submit an algorithm document. This document should be named '''algorithm_[student_id].txt'''. This file should be plaintext. The document will contain two sections: * A description of how the "after()" function works. The "after()" function is provided to you in a1_template.py. Open the file, and use clear English to describe what line of code does in such a way that a competent programmer could reproduce the code without seeing it firsthand. * You will then apply the same principles to create an algorithm for "before()", and "dbda()". Inside the code, if you are calling another function like "leap_year", you may simply describe what the function will return, and not the operation of the function itself. * This file will be submitted to Blackboard a week after the assignment goes live, and should be your first priority. The object of the milestone is not to have a 100% perfect algorithm, but to plan ahead and anticipate challenges and issues with the assignment. The milestone will also give your professor an opportunity for feedback.* [https://simple.m.wikipedia.org/wiki/Algorithm Here is an basic introduction to Algorithm]* While you are working on the step-by-step instructions, note that there are different number of days in each month and some years have 365 days and some years have 366 days.* You should also do some research to find out when we started using the Calendar in the current form. (This will pose a limit on the validity of your algorithm.)
== The Assignment Clone Your Repo (due November 3ASAP) == * As stated before, your code will be inside the file "a1_[studentid].py". The first step will be to clone the Assignment 1 repository. The invite link will be provided to you by your professor. Once The repo will contain a check script, a README file, and the file where you clone the repository, run this command: "cp a1_template.py a1_[studentid].py". (Replace studentid with will enter your myseneca username). Begin writing the content that is required. Additional requirements are outlined belowcode.
== The Debrief First Milestone (due November 12February 14) ==This document, like For the algorithm document, first milestone you will be submitted have two functions to Blackboard one week after the assignmentcomplete. Answer the following questions:* Research Python modules that you could have used to accomplish the same goals as the today() <code>call_du_sub</code> will take one argument and leap_year() functionsreturn a list. * Which solution is preferable, in terms of performance? Which solution The argument is preferable, in terms of programmer hours? (which solution would take longer for a programmer target directory. The function will use <code>subprocess.Popen</code> to implement?)* Which approach would be preferable in run the "real world"? Why is it useful to try creating our own algorithm?command <b>du -d l <target_directory></b>. * What challenges did you encounter during the assignment, <code>percent_to_graph</code> will take two arguments and what resources did you use to solve your issues? (help from classmates, help from Stackoverflow, debuggers, etc.)* Additionally, your professor may have questions specific to your submission. You should answer these questions as wellreturn a string.
In order to complete <code>percent_to_graph()</code>, it's helpful to know the equation for converting a number from one scale to another.
[[File:Scaling-formula.png]]
In this equation, ``x`` refers to your input value percent and ``y`` will refer to the number of symbols to print. The max of percent is 100 and the min of percent is 0.
Be sure that you are rounding to an integer, and then print that number of symbols to represent the percentage. The number of spaces that you print will be the inverse.
== Tests and Test results ==You must name your python 3 script as <code>a1_[Student_id].py</code>. The following examples assumes that the student_id is rchan.The script should accept two command line arguments, the first one is the date in "YYYY-MM-DD" format, and the second one is the number of day from the given date, a positive value indicates the number of days after the given date, and a negative value indicates the number of days before the given date. There is an optional flag called --step which can be provided at the command line that makes the program print out all dates until the target date. If the "YYYY-MM-DD" format is broken, your script should give an appropriate error message. Invalid months (>12) or invalid days of month(different for each month), should be detected and give appropriate error messages. For examples:* <b><code>python3 a1_rchan.py 01-01-2019 02-01-2019</code></b>, and the output should be<br /> 1* <b><code>python3 a1_rchan.py 01-01-2019 31-12-2018</code></b>, and the output should be<br /> -1* <b><code>python3 a1_rchan.py 01-06-2020</code></b>, and since today is June 3, functions with the output should be<br /> 2 * <b><code>python3 a1_rchan.py 01-01-2019 01-01-2020</code></b>, and the output should be<br /> 365* <b><code>python3 a1_rchanPython interpreter.py 01-01-2021 01-01-2020 </code></b>, and the output should be<br /> -366* <b>Use <code>python3 a1_rchan.py 01-13-2018</code></b>, and the output should be<br /> Errorthen: wrong month entered* <b><code>python3 a1_rchan.py 99-01-2020 01-01-2020</code></b>, and the output should be<br /> Error: wrong day entered import duim* <b><code>python3 a1_rchan duim.py 2018 2</code></b>percent_to_graph(50, and the output should be<br /> Error: wrong date entered10)
If there is too few or too many command line arguments givenTo test with the check script, display run the proper usage:* <code>Usagefollowing: a1_rchan.py DD-MM-YYYY [DD-MM-YYYY] >/code>
== Script structure and sample template ==<code>python3 checkA1.py -f -v TestPercent</code>
The following is == Second Milestone (due February 21) ==For the second milestone you will have one more function to complete.* <code>create_dir_dict</code> will take your list from <code>call_du_sub</code> and return a dictionary. ** Every item in your list should create a key in your dictionary.** Your dictionary values should be a brief description number of each function:bytes.
* The dbda() function should be the main function of your script. The dbda() function will take two dates in "DD-MM-YYYY" format, and return an integer that corresponds to the number of days between the given dates. If the start date is earlier than the stop date, the number is positive. If start date is later than the stop date, the number is negative. Your dbda() function should delegate the actual calculation of the target date to either the after() function or the before() function. * The today() function will be called if the user has not specified a second argument. It will return '''your Linux computerFor example: <code>{'s /usr/lib/local time''' in the format DD-MM-YYYY. Hint: you may need to read man pages for a shell command in order to return a usable date. You may also use string formatting to modify output.* The before() function will take a date in "DD-MM-YYYY" format and return the date of the previous day in the same format.* The after() function will take a date in "DD-MM-YYYY" format and return the date of the next day in the same format. Next paragraph is a sample python 33400}</code for the after() function. To earn the maximum possible mark for the assignment, you should modify the sample after() function to make use of the days_in_mon() function.>* The leap_year() function will take a year in "YYYY" format, and return True if the given year is a leap year, otherwise return False. * The valid_date() function will take a date in "DD-MM-YYYY" format, and return True if the given date is a valid date, otherwise return False plus an appropriate status message. The valid_date() function should make use of the days_in_mon() function.* The days_in_mon() function will take a year in "YYYY" formatAgain, and return a dictionary object which contains the total number of days in each month for the given year. The days_in_mon() function should make use of the leap_year() function.* The usage() function will take no argument and return a string describing the usage of test using your Python interpreter or the check script.
=== Sample code for To run the after() function ===<pre># Return check script, enter the date in DD-MM-YYYY after the given day# def after(today): if len(today) != 10: return '00-00-0000' elsefollowing: str_day, str_month, str_year = today.split('-') year = int(str_year) month = int(str_month) day = int(str_day)
lyear = year % 4 if lyear == 0: feb_max = 29 # this is a leap year else: feb_max = 28 # this is not a leap year<code>python checkA1.py -f -v TestDirDict</code>
lyear = year % 100= Minimum Viable Product == Once you have achieved the Milestones, you will have to do the following to get a minimum viable product: * In your <code>if lyear __name__ == 0'__main__'</code> block, you will have to check command line arguments. ** If the user has entered no command line argument, use the current directory.** If the user has entered more than one argument, or their argument isn't a valid directory, print an error message.** Otherwise, the argument will be your target directory.* Call <code>call_du_sub</code> with the target directory.* Pass the return value from that function to <code>create_dir_dict</code>* You may wish to create one or more functions to do the following: feb_max = 28 # this is ** Use the total size of the target directory to calculate percentage.** For each subdirectory of target directory, you will need to calculate a percentage, using the total of the target directory.** Once you've calculated percentage, call <code>percent_to_graph</code> with a max_size of your choice. ** For every subdirectory, print <i>at least</i> the percent, the bar graph, and the name of the subdirectory.** The target directory <b>should not </b> have a leap yearbar graph.
lyear = year % 400 if lyear =Additional Features = 0: feb_max = 29 # this is a leap year
tmp_day = day + 1 # next dayAfter completing the above, you are expected to add some additional features. Some improvements you could make are:
mon_max = { 1:31, 2:feb_max, 3:31, 4:30, 5:31, 6:30, 7:31, 8:31, 9:30, 10:31, 11:30, 12:31}* Format the output in a way that is easy to read. if tmp_day > mon_max[month]:* Add colour to the output. to_day = tmp_day % mon_max[month] # if tmp_day > this month's max* Add more error checking, reset print a usage message to 1the user. tmp_month = month + 1 else* Convert bytes to a human-readable format. NOTE:This doesn't have to be 100% accurate to get marks. to_day = tmp_day* Accept more options from the user. tmp_month = month + 0* Sort the output by percentage, or by filename.
if tmp_month > 12It is expected that the additional features you provided should be useful, non-trivial, they should not require super-user privileges and should not require the installation of additional packages to work. (ie: to_month = 1 year = year + 1 else: to_month = tmp_month + 0I shouldn't have to run pip to make your assignment work).
next_date = str= The Assignment (to_day)+"-"+str(to_monthdue March 7, 11:59pm)==* Be sure to make your final commit before the deadline.* Then, copy the contents of your <b>duim.py</b> file into a Word document, and submit it to Blackboard.zfill(2)+"-"+str(year)<i>I will use GitHub to evaluate your deadline, but submitting to Blackboard tells me that you wish to be evaluated.zfill(2) return next_date</prei>
= Rubric =
| Program Authorship Declaration || 5 ||
|-
| Check script passed required functions design || 30 5 ||
|-
| today() function design required functions readability || 2 5 ||
|-
| before() function main loop design || 5 10 ||
|-
| dbda() function design main loop readability || 10 ||
|-
| script level docstring output function design || 5 ||
|-
| leap_year() output function design readability || 2 5 ||
|-
| valid_date() function design additional features implemented || 5 20 ||
|-
| usage() function design docstrings and comments || 1 5 ||
|-
| First Milestone ||10||
|-
| Reflection Essay Second Milestone || 10 ||
|-
| github.com repository: Commit messages and use ||1510 ||
|-
|'''Total''' || 100 ||
= Due Date and Final Submission requirement =
Check with your professor for the due date for your section.
Please submit the following files by the due date:
* [ ] your algorithm document, named as 'algorithm_username.txt', to Blackboard.* [ ] your python script, named as 'a1_[seneca-id]duim.py', should be included in your repository, and also '''submitted to Blackboard.'''* [ ] the output of the checking script checkA1.py, named as 'a1_output.txt', should be included in your repository.* [ ] your debrief document should be submitted to Blackboardby March 7 at 11:59pm.
