Skip to main content

No project description provided

Project description

Batch Prediction Pipeline

Check out this Medium article for more details about this module.

Create Environment File

~/energy-forecasting $ cp .env.default .env

The command cp .env.default .env is used to create a copy of the .env.default file and name it .env. In many projects, the .env file is used to store environment variables that the application needs to run. The .env.default file is usually a template that includes all the environment variables that the application expects, but with default values. By copying it to .env, you can customize these values for your own environment.

Set Up the ML_PIPELINE_ROOT_DIR Variable

~/energy-forecasting $ export ML_PIPELINE_ROOT_DIR=$(pwd)

The command export ML_PIPELINE_ROOT_DIR=$(pwd) is setting the value of the ML_PIPELINE_ROOT_DIR environment variable to the current directory. In this context, $(pwd) is a command substitution that gets replaced with the output of the pwd command, which prints the path of the current directory. The export command then makes this variable available to child processes of the current shell.

In essence, ML_PIPELINE_ROOT_DIR is an environment variable that is set to the path of the current directory. This can be useful for scripts or programs that need to reference the root directory of the ML pipeline, as they can simply refer to ML_PIPELINE_ROOT_DIR instead of needing to know the exact path.

Install for Development

The batch prediction pipeline uses the training pipeline module as a dependency. Thus, as a first step, we must ensure that the training pipeline module is published to our private PyPi server.

NOTE: Make sure that your private PyPi server is running. Check the Usage section if it isn't.

Build & publish the training-pipeline to your private PyPi server:

cd training-pipeline
poetry build
poetry publish -r my-pypi
cd ..

Install the virtual environment for batch-prediction-pipeline:

~/energy-forecasting                           $ cd batch-prediction-pipeline && rm poetry.lock
~/energy-forecasting/batch-prediction-pipeline $ bash ../scripts/devops/virtual_environment/poetry_install.sh
~/energy-forecasting/batch-prediction-pipeline $ source .venv/bin/activate

Check the Set Up Additional Tools and Usage sections to see how to set up the additional tools and credentials you need to run this project.

Usage for Development

To start batch prediction script, run:

~/energy-forecasting/batch-prediction-pipeline $ python -m batch_prediction_pipeline.batch

To compute the monitoring metrics based, run the following:

~/energy-forecasting/batch-prediction-pipeline $ python -m batch_prediction_pipeline.monitoring

NOTE: Be careful to set the ML_PIPELINE_ROOT_DIR variable as explained in this section.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

g_batch_prediction_pipeline-0.3.0.tar.gz (8.2 kB view details)

Uploaded Source

Built Distribution

File details

Details for the file g_batch_prediction_pipeline-0.3.0.tar.gz.

File metadata

File hashes

Hashes for g_batch_prediction_pipeline-0.3.0.tar.gz
Algorithm Hash digest
SHA256 8ca12b4ccb1ab76143baf9b06881b44ca9536bf42f8ef5269086e7ae1aab1f9d
MD5 0443fff72b8f7561ee3cf2aa32f0a5d4
BLAKE2b-256 36c594af2522bccee57b02e6b79fb18b8363ee19b0775e54494ede274a3f4d9c

See more details on using hashes here.

File details

Details for the file g_batch_prediction_pipeline-0.3.0-py3-none-any.whl.

File metadata

File hashes

Hashes for g_batch_prediction_pipeline-0.3.0-py3-none-any.whl
Algorithm Hash digest
SHA256 445247c6e65b16347a22bdb39f1b4e59a30a5dcede5f01b82258b6a7b3f89215
MD5 7c679500be9b70a4a9657b399ba32dab
BLAKE2b-256 34a0f3d82c7e76ba6bdc22faedf4504f1d2e6a2cfe6750c28dcc408e6b4f63ac

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page