CST383 - Week 3

CST383 - Week 3

    This week we learned more about how to work in Colab/Jupyter notebook. I personally used Jupyter because I thought self-hosted material is more appropriate for my use case. I think this notebook style of coding is very useful, because I can test only a single block of code at a time rather than the full file. 

    We started to learn how to code Pyplot visualizations of data, which is very nice. I am a visual learner so these exercises were very helpful for me to understand these concepts better. I didn't have much difficulty understanding these concepts to complete the homework, though I know I will need to read further into graphing two continuous variables in the coming weeks. A few things stood out to me to remember:
  • Use a semicolon ( ; ) after the last plotting statement or use plt.show() at the end of the code block to prevent matplotlib from automatically adding text before a graph.
  • Use plt.xlabel() or plt.ylabel() to label the x or y axis. For box plots, the x axis is automatically set as the variable name - use plt.xticks([]) to empty it. plt.xticks(['a','b','c']) will add 3 increment labels 'a', 'b', 'c' to the x axis. plt.xlabel() will add a label below the x-ticks on the x axis.
  • You can use f"{x:.2f}" to format a number x to 2 decimal places.
  • To include a number in a range, for example df['column1'].plot.hist(bins=range(10,111,10)) this starts at 10 and evenly spaces out 10 width bins (third number in range()), up to 110 (second number in range() is not inclusive, so we must add 1 to include 110).

Comments

Post a Comment

Popular posts from this blog

CST300 - Week 4

Week 4 has been busy! I have gotten work done a lot later than I would have liked. Part 1: Education Goals My educational goals would be to expand my knowledge about Javascript. The most tangible project to put this in practice would be to create a simple interactable website, possibly using React as a frontend. One of my ideas for a capstone project would be to create a website for a tabletop game I am developing, so the practice would be great for it.   The first step would be to learn about networking -- CST311: Intro to Computer Networking and CST336: Internet Programming would be where I hone these skills. Before these classes, I would like to create a single-task web app as a practice. It would have a starting list of about 20 items, and allow the user to arrange them into 6 specific item slots, like a digital pin board. Then, once I am in these classes, I will look back at this project and see what I can do differently or what I have learned since then.   My web develop...
Read more

CST334 - Week 6

Week 6 Reflection This week, we learned more about semaphores, and the bugs that are commonly faced in concurrency, such as deadlocks.  Semaphores are a synchronization primitive that has a modifiable integer value. The behavior of the semaphore is determined by this value. They can be used as both locks and condition variables for concurrency.  sem_wait() and sem_post() are used to interact with a semaphore. sem_wait() waits for a condition to be met, while sem_post() increments the value of the semaphore, then wakes a waiting thread. If a semaphore's value is negative, this number is equal to the number of waiting threads. For example, -4 equals four waiting threads, incrementing by 1 will change it to -3, waking one thread and now resulting in three waiting threads. Concurrency creates bugs that are difficult or costly to fix correctly. Non-deadlock bugs include atomicity violations and order violations. Atomicity violations occur when instructions that sho...
Read more

CST334 - Week 5

Week 5 Reflection      In this week, I learned a great deal about concurrency, threads, and best practices on how to keep threads managed efficiently. A thread is seen as a process that can share the same address space as another thread, and access the same data, rather than needing to occupy a different address space. Multi-threading is handling multiple threads in the same address space using thread control blocks (TCBs) to store thread states. For multi-threaded processes, each thread has its own stack, called the thread-local storage.       In the aside, four key terms are highlighted:  critical section: Code that accesses a shared resource, like a data structure or variable.  race condition (aka data race): If multiple threads enter the critical section at the same time, a race condition occurs. These threads could be executed in any order, leading to the program becoming indeterminate. indeterminate program: A program with one or more r...
Read more