https://github.com/chris-santiago/aafm

Enhanced Chilean Mutual Fund Data Explorer

https://github.com/chris-santiago/aafm

Science Score: 10.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
    4 of 5 committers (80.0%) from academic institutions
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (14.2%) to scientific vocabulary

Keywords

anomaly-detection chilean clustering efficient-frontier modern-portfolio-theory mutual-funds t-sne
Last synced: 5 months ago · JSON representation

Repository

Enhanced Chilean Mutual Fund Data Explorer

Basic Info
  • Host: GitHub
  • Owner: chris-santiago
  • Language: Jupyter Notebook
  • Default Branch: master
  • Homepage:
  • Size: 162 MB
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Topics
anomaly-detection chilean clustering efficient-frontier modern-portfolio-theory mutual-funds t-sne
Created over 3 years ago · Last pushed over 3 years ago

https://github.com/chris-santiago/aafm/blob/master/

# Table Of Contents

* [Getting Started - Overview](#Getting%20Started%20-%20Overview)
    * [Getting Started - Without Docker](#Getting%20Started%20-%20Without%20Docker)
    * [Getting Started -  With Docker](#Getting%20Started%20-%20With%20Docker)
* [Getting Started - ETL](#Getting%20Started%20-%20ETL)


# Getting Started - Overview

This project can be developed locally in two ways (primarily).
1) By installation of all code/tools/data/etc. locally on your machine (this is currently the most common workflow).
2) By installing Docker, then installing all code/tool/etc. into a Docker container, treating the new Docker container as your isolated development environment.

Why do we need two ways of doing things? The short answer is that we don't _need_ two ways of doing things, but there are pros and cons to each approach. [This document](https://www.ibm.com/cloud/learn/containerization) by IBM covers containerization and why someone would consider leveraging it (it's a bit long, but the following table hits on someone of the differences). The introductory sections of this video are quite helpful as well https://www.youtube.com/watch?v=KFyRLxiRKAc

|Aspect|Without Containers|With Containers|
|---|---|---|
|Largely Avoids "Works On My Machine"|No|**Yes**|
|Complexity|**Low**|Medium|
|Getting Started|**Fast**|**Medium-Slow then becomes Fast**|
|Portability|More Work|**Low Work**|
|Consistency|High Work|**Low Work**|
|Agility|Low|**High**|
|Isolation|Low|**High**|

For me (Collin), I chose dockerized development because I can run different versions of software in isolation.

Once you've chosen which style of development you would like to persue, go to [Getting Started - Without Docker](#Getting%20Started%20-%20Without%20Docker) xor [Getting Started -  With Docker](#Getting%20Started%20-%20With%20Docker) which ever matches your needs.


# Getting Started - Without Docker

Clone this repo and then install the project package:

```bash
cd aafm
pip install -e .
```


# Getting Started - With Docker

_This section assumes you're using VS Code for development_

1) Go through this document or vidoe to familiarize yourself with containerized development https://code.visualstudio.com/docs/remote/containers or https://www.youtube.com/watch?v=KFyRLxiRKAc 
2) Add the `Remote - Containers` extension to VS Code (https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) 
2) Clone this repository
3) Open the root folder (aafm) in a container. See: https://code.visualstudio.com/docs/remote/containers#_quick-start-open-an-existing-folder-in-a-container or the video in step 1.
    * The container has been configured to include Python 3.8, and Jupyter, meaning both of those will work out of the box without further configuration.


# Getting Started - ETL

ETL (Extract Transform Load) basically just means data prep. Load some data from somewhere, transform it into a useful shape, then store it somewhere else.

1) From Microsoft Teams, navigate to Files, then the Data Folder, then download `data.7z`
    * You will need a utility (or library) such as 7-zip to decompress the file.
    * Why 7z? Because it has much better compression (LZMA2) than zip (DEFLATE).
2) Extract the contents of `data.7z` into this project at `./data/raw/daily/`.
3) Open `./notebooks/extract.ipynb` using Jupyter Notebooks or VS Code Notebooks.
    * If you're using our Docker Container for development, the right tools have already been added.
      Simply open `extract.ipynb` in VS Code and wait for the proper UI to load.
4) Run each notebook cell on it's own to see how they work, or run them all.

Owner

  • Name: Chris Santiago
  • Login: chris-santiago
  • Kind: user

GitHub Events

Total
Last Year

Committers

Last synced: over 1 year ago

All Time
  • Total Commits: 73
  • Total Committers: 5
  • Avg Commits per committer: 14.6
  • Development Distribution Score (DDS): 0.384
Past Year
  • Commits: 0
  • Committers: 0
  • Avg Commits per committer: 0.0
  • Development Distribution Score (DDS): 0.0
Top Committers
Name Email Commits
csantiago37 c****o@g****u 45
ckruger3 c****3@g****u 20
Nagasree Chelamalla (nchelamalla3) n****3@g****u 6
Flynn, Shannon Rose s****5@g****u 1
csantiago37 c****o@p****n 1
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 11 months ago

All Time
  • Total issues: 0
  • Total pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Total issue authors: 0
  • Total pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
Top Labels
Issue Labels
Pull Request Labels