Forem: d

Plotting out SORA

Sat, 30 Nov 2024 13:13:38 +0000

Let's generate a graph using SORA 3M and SORA 1M data. First download the dataset, it should come in the form of a csv.
Then proceed to clean the dataLet's generate a graph using SORA 3M and SORA 1M data.

First download the dataset, it should come in the form of a csv.
Then proceed to clean the data

import pandas as pd

df = pd.read_csv("sora.csv")
df = df[df["Compount SORA - 1 month"] != '-']
df = df[df["Compount SORA - 3month"] != '-']
df = df.drop(columns=["SORA Value Date", "year", "month"])
df.to_csv("sora (edited).csv", index=False)

Then plot out the data

import pandas as pd
import plotly.graph_objects as go

df['Compound SORA - 3 month'] = pd.to_numeric(df['Compound SORA - 3 month'], errors="coerce")

fig = go.Figure()

fig.add_trace(
    go.Scatter(
        x=df['SORA Publication Date'],
        y=df['Compound SORA - 3 month'],
        marker=dict(color="Blue", symbol="circle", size=2),
        name="SORA - 3M"
    )
)

fig.add_trace(
    go.Scatter(
        x=df['SORA Publication Date'],
        y=df['Compound SORA - 1 month'],
        marker=dict(color="Black", symbol="circle", size=1),
        name="SORA - 1M"
    )
)

This should then give you the result

The original version of this article was published on medium.

Manual Workflows in GitLab

Sun, 03 Mar 2024 16:14:51 +0000

GitLab's manual workflows offers users the control to decide when the workflow should commence. The workflow is often defined in a gitlab-ci.yml file. The simplest template looks like the following.

stages:

deploy git_status: stage: deploy script:

echo "hello"

ls

pwd

git pull origin main

git status when: manual allow_failure: true

stages: Defines the stages in our CI/CD pipeline. In this scenario, we have a single stage named "deploy," signifying the final phase before deployment.
git_status: The identifier for our job, customizable to suit our project's needs.
script: Specifies the commands to be executed by GitLab upon job activation
when: manual: mandates manual intervention before proceeding
allow_failure: true: Provides leniency in the event of job failure

Once the above changes have been committed, head over to the pipelines section. Build > Pipelines and click on the "Play" button adjacent to the job.

This can be used to create a release for a project or for any other manual inspecting of the project such as running a lighthouse evaluation on a reactjs project.

This article is also published in https://parkerrobert.medium.com/manual-workflows-in-gitlab-d6addb70d389

VSCode Shortcuts

Sun, 03 Mar 2024 15:19:14 +0000

A good rule of thumb to being an efficient programmer is trying to be one with the tool you are using. For most people one of the most popular IDEs out there at the moment is VSCode.

In order to supercharge your VSCode usage here are some shortcuts that go a long way.

Photo by Mohammad Rahmani on Unsplash

Multiple cursors

In order to enable multiple cursors in VSCode, press ALT + SHIFT + up/down or OPTION + COMMAND + up/down on a MAC. This is especially useful for writing duplicated code such as switch statements for example.
multiple cursors

Go to a specific line

This works wonder when trying to fix linting errors or compiling errors. If the compiler tells you there is a problem in line 7, then hitting CTRL + p or COMMAND + p, followed by ":" and the line number allows you to quickly head to that line.

Go to a file

This is similar to the one above, but instead of adding a colon at the end simply type the file name. CTRL + p or COMMAND + p followed by the file name that you would like.

Search through all files

If there is a term that you would like to find in all the files just to a CTRL + SHIFT + f or COMMAND + SHIFT + f

Search through current file

If there is a term that you would like to find in the current file just to a CTRL + f or COMMAND + f

Change next few occurences of the word

If there is a term that you would like to find in the current file just to a CTRL + d or COMMAND + d multiple times

Open README View

It can be difficult to read READMEs at times. Instead of reading the markdown directly try this instead. CTRL + k followed by v

The above article was originally published on https://parkerrobert.medium.com/vscode-shortcuts-57a145a7772f