cst383 - week 3

    This week covered a large amount of topics related to data visualization and statistical analysis using pandas. We learned different plotting systems, how to display information in meaningful ways using , how to customize visualizations, and how to perform calculations using the data. At first it was a little overwhelming because there were many different visualization methods and understanding where each was best used depending on the different types of data. It took me some time and a decent amount of review before I became more comfortable recognizing where certain plotting systems are most useful or how to interpret them effectively.

    We also covered concepts like correlation and covariance. One thing I found especially interesting was the idea that even though data may appear objective and straightforward, it still requires critical thinking to interpret correctly. Identifying correlation does not necessarily reveal the full truth behind the data, and relationships between variables can sometimes be misleading if context is ignored. This made me realize that data analysis is not just about collecting numbers, but also about carefully reasoning about what those numbers actually represent.

    Distributions and variance also stood out to me as incredibly important for being able to identify meaningful patterns and inconsistencies from data. Looking at how data is spread out can reveal information that might not be obvious from averages alone. It helped reinforce the idea that understanding the shape and variability of data is just as important for analysis as understanding individual values.

    There was a lot of material to retain this week, I feel that I can clearly see why data science is such an important part of so many careers.

Comments

Post a Comment

Popular posts from this blog

CST334 Week 2

    This week has been a great introduction to how CPU process selection works in operating systems. We covered a range of scheduling algorithms, including FIFO (First In, First Out), LIFO (Last In, First Out), Shortest Job First (SJF), and Round Robin (RR). I learned how each algorithm has its own strategy for picking which process should run next, and how these choices affect system performance and metrics like response times.      I also learned to calculating those performance metrics such as response time, turnaround time, average arrival time, and average turnaround time. For Round Robin scheduling in particular, I learned how to calculate how long a process will stay in the system based on the time slice and the number of other processes in the queue. These exercises helped me understand the mechanics of how schedulers work and why the design choices made are so important.      One of the most interesting parts was comparing the pros and ...
Read more

CST334 Week 5

     This week I focused on concurrency and how it allows processes to run multiple threads in parallel, allowing tasks to be handled in the background while the main application continues. While I’ve previously worked with multithreading in Java, learning how the operating system manages concurrency gave me a better understanding of how multithreading works in the CPU. I learned that threads can share certain resources, such as virtual address space which makes communication between them efficient, but also introduces its own challenges.      One of the key concepts I learned was nondeterminism in multithreaded programs. Even if two threads call the same function, the order in which memory is accessed and modified can change which can lead to different outcomes every time the program runs. This unpredictability can cause bugs that are hard to reproduce and debug.      To address this, we use thread synchronization APIs like locks, or mutexes...
Read more

CST334 Week 6

       This week we continued concurrent programming and synchronization concepts and built on the ideas from last week. One of the first things I learned about was binder buffer coding, which was about how data can be shared and communicated between different parts of a system or between different threads. It's a used when dealing with message passing or structured data flow. Systems with modular or layered designs can make use of this to communicate with other parts of the system.    After  that, I learned about the concept of semaphores. Semaphores are a core component in concurrent programming as they act as signaling mechanisms used to control access to shared resources. The main idea of semaphores are integer variables protected by atomic operations like wait() and signal(). A semaphore can be used to limit the number of threads that access a resource such as a database connection pool or a bounded buffer to ensure that the variables remain safe ...
Read more