Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ujstor/streamlit-working-hours
The analysis pipeline involves combining the data forms, performing data cleaning, and starning streamlit server for statistical analysis.
https://github.com/ujstor/streamlit-working-hours
streamlit
Last synced: about 1 month ago
JSON representation
The analysis pipeline involves combining the data forms, performing data cleaning, and starning streamlit server for statistical analysis.
- Host: GitHub
- URL: https://github.com/ujstor/streamlit-working-hours
- Owner: Ujstor
- Created: 2023-08-08T21:26:25.000Z (over 1 year ago)
- Default Branch: master
- Last Pushed: 2023-11-04T15:43:40.000Z (about 1 year ago)
- Last Synced: 2023-11-04T16:36:12.475Z (about 1 year ago)
- Topics: streamlit
- Language: Jupyter Notebook
- Homepage: https://working-hours.astipan.com/
- Size: 1.08 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Working Hours Data Set Analysis
This repository contains data sets and analysis scripts for working hours data spanning multiple years. The raw data is divided into three forms and stored in separate Excel files for each month. The analysis pipeline involves combining the data forms, performing data cleaning, and starning streamlit server for statistical analysis. The final analysis includes various visualizations, statistical measures, and insights into the working hours data.
## Data
The raw data is organized as follows:
`./raw_data`: Contains the three forms of raw data, each stored in separate folders:
-`data_form1`: Contains the raw data for form 1. (5.2021-9.2022)
-`data_form2`: Contains the raw data for form 2. (10.2022-present)
-`data_form3`: Contains the raw data for form 3. (1.2021-4.2021)
After running `run_data_procsing.bat`, the combined data sets for each form are stored in the following files:
- `./data/combined_dataform2.csv`
- `./data/combined_dataform1.csv`
- `./data/combined_dataform3.csv`
The cleaning process involves extracting relevant columns, handling missing values, and ensuring data consistency.
The cleaned and combined data sets from each form are merged into a single CSV file:
- `./data/final_data.csv`
You can now view your Streamlit app in your browser.
Local URL: http://localhost:8501
Quit app `ctrl-c`
# Python Environment Setup and Dependency Installation
run `install_python.bat` script automates the setup process for a Python project by performing the following steps:
1. Checks if Python is installed. If not, it installs Python using the "winget" package manager.
2. Checks if a virtual environment folder named 'env' exists. If not, it creates one.
3. Activates the virtual environment.
4. Installs Python dependencies listed in the `requirements.txt` file using the "pip" package manager.
# Docker
To build the Docker image from the code, run:
```
docker compose -f .\docker-compose-dev.yml up
```
If you want to pull the image from the Docker repository instead, use:
```
docker compose -f .\docker-compose-prod.yml up
```
Image is automatically built and deployed through the Jenkins pipeline after tests have passed and are merged into the master branch.
# Jenkins Pipeline
Pipeline is designed to automate the build, test and deployment process for a project. It includes several stages that are executed when the pipeline is triggered. The pipeline assumes the main development branch is named "master" and tailors its actions accordingly.
### Pipeline Stages
1. **Checkout Code**: This stage fetches the project's source code from a specified Git repository and branch (assumes "master" branch by default).
2. **Test**: Runs tests on the code to ensure its correctness.
3. **Generate Docker Image Tag**: Generates a Docker image tag if the pipeline is running on the "master" branch. The image tag format is determined by the version part specified (Patch, Minor, Major).
4. **Build**: Builds a Docker image using the generated tag. This stage also requires the "master" branch to execute.
5. **Deploy**: Pushes the Docker image to a Docker Hub repository. It is executed only on the "master" branch.
6. **Environment Cleanup**: Cleans up the Docker image. Like the previous stages, it runs exclusively on the "master" branch.
### Skipping Stages
If the branch is not "master," the stages related to Docker image generation, build, deployment, and cleanup will be skipped, ensuring the pipeline continues without failure.