With the detectors currently off, LIGO has detected and gathered an abundance of data from the second observing run (O2). Some of which, captures the most recent triggers that are potential candidates for future gravitational waves, are analyzed more thoroughly. My responsibility as a student researcher is to perform independent checks on four of the most recent Compact Binary Coalescence (CBC) triggers. In order to do so, I compare the \(h(t)\) Omega scans of these events to the Gravity Spy classes. Omega scans are a detector characterization tool to help measure the Signal-to-Noise-Ratio (SNR) of transient noises during detections. This helps scientists distinguish the difference between a gravitational wave signal, which looks like a `chirp' versus a glitch in the data. Gravity Spy is a citizen science program that helps LIGO in classifying glitches to improve machine learning for gravitational wave signals. For each event I determine if it looks like one of the known categories of solved or unsolved glitches seen in the Advanced LIGO detectors? My results are then recorded in the O2 event detection checklist. Omega scans are a `burst-type' search pipeline that detect glitches efficiently. The Omega scan is labeled using time measured in seconds on the x-axis, frequency measured in Hz on the y-axis and the signal measured is normalized to demonstrate how `loud' the noise is.
The kernel is a computer program that has complete control over the operating system. It handles the input/output requests and translates them into data-processing instructions for the CPU. It handles not only the memory, but also peripherals.
The kernel controls the tasks that are managed in the running system, some of these are running processes, hardware management and handling interrupts, in the kernel space. On the other hand, the user performs in the user space. This separation helps to prevent data interfering that can cause instability and slowness, or worse, malfunctioning application programs that can crash the entire operating system.
The process scheduler decides which is the next task to run. In the following project we analyzed the behavior of the scheduler changing the default value of the runtime scheduling, this value is 950000µs for the scheduler real time running variable. According to this, 5% of the CPU time is reserved for processes that are not running under a realtime or deadline scheduling policy. On this project, this value specifies how much of the period time could be used by real-time and deadline scheduled processes on the system.
This is the LaTeX template for Wiley StatsRef. Please refer to the journal’s author guidelines in order to confirm your manuscript adheres to the journal’s requirements for submissions.
Once your manuscript is complete, simply use the "Submit to Journal" option in the Overleaf editor to submit your files directly to the journal for processing.
If you're new to LaTeX, check out our free online introduction to help you get started, or please get in touch if you have any questions.