whipser-container
https://github.com/in-for-disaster-analytics/whipser-container
Science Score: 44.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (13.0%) to scientific vocabulary
Repository
Basic Info
- Host: GitHub
- Owner: In-For-Disaster-Analytics
- Language: Shell
- Default Branch: main
- Size: 154 KB
Statistics
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 1
- Releases: 0
Metadata Files
README.md
This template is the first in a series of tutorials that will guide you through the process of creating a cookbook and running it on TACC systems. From simple ones that run a command to more complex ones that run a Python using conda or a Jupyter Notebook.
Requirements
- A GitHub account
- TACC account. If you don't have one, you can request one here
- To access TACC systems, you should have an allocation
Template Overview
This template creates a simple cookbook that will run a job on a TACC cluster using two parameters/arguments, Greeting and Target, and obtain the output via a UI, saving it to a file named out.txt.


How does it work?
app.jsonfile: contains the definition of the Tapis application, including the application's name, description, Docker image, input files, and advanced options.Dockerfile: a Docker image is built from theDockerfile. The Docker image defines the runtime environment for the application and the files that will be used by the application.run.sh: contains all the commands that will be executed on the TACC cluster.
Job run script
The run.sh file is used to run the commands.
```bash
!/bin/bash
Greeting=$1 Target=$2
FULLGREETING="${Greeting} ${Target}. My name is ${tapisJobOwner}" echo "$FULL_GREETING"
echo $FULLGREETING > $tapisExecSystemOutputDir/out.txt ```
The run.sh script receives two parameters, Greeting and Target, and uses them to create a message that will be saved to a file named out.txt.
Also, the script uses the _tapisExecSystemOutputDir variable, which contains the path where the application writes the output files.
Create your Cookbook
Create a new repository
- Click on the "Use this template" button to create a new repository
- Fill in the form with the information for your new repository
Build the Docker image
You can skip this step if you don't want to build the Docker image yourself. You can use the Docker image from the Docker Hub.
- Clone the repository
- Build the Docker image using the command below
bash
docker build -t cookbook-python .
- Push the Docker image to a container registry
bash
docker tag cookbook-python <your-registry>/cookbook-python
docker push <your-registry>/cookbook-python
Modify the app.json file
Each app has a unique id and description. So, you should change these fields to match your app's name and description.
- Download the
app.jsonfile - Change the values
idanddescriptionfields with the name and description as you wish. - If you built the Docker image, change the
containerImagefield with the image name you used.
Create a New Application on the Cookbook UI
- Go to Cookbook UI
- Click on the "Create Application" button
- Fill in the form with the information from your
app.jsonfile - Click "Create Application"
- A new application will be created, and you will be redirected to the application's page
Run your Cookbook
- Go to the application's page on the Cookbook UI, if you are not already there
- Click on the "Run" button on the right side of the page. This will open the Portal UI
- Select the parameters for your job

Check the Output
- After the job finishes, you can check the output by clicking on the "Output location" link on the job's page

- You will be redirected to the output location, where you can see the output files generated by the job

- Click on a file to see its content. In this case, the file is named
out.txt
Next templates
Authors
William Mobley - wmobley@tacc.utexas.edu Maximiliano Osorio
Owner
- Name: In-For-Disaster-Analytics
- Login: In-For-Disaster-Analytics
- Kind: organization
- Repositories: 1
- Profile: https://github.com/In-For-Disaster-Analytics
Citation (CITATION.cff)
# This CITATION.cff file was generated with cffinit.
# Visit https://bit.ly/cffinit to generate yours today!
cff-version: 1.2.0
title: Cookbook-Tutorial-Template
message: >-
If you use this software, please cite it using the
metadata from this file.
type: software
authors:
- given-names: Maximiliano
family-names: Osorio
orcid: 'https://orcid.org/0000-0002-3611-6510'
- given-names: William
family-names: Mobley
email: wmobley@tacc.utexas.edu
affiliation: Texas Advanced Computing Center
orcid: 'https://orcid.org/0000-0003-1783-0599'
- given-names: Lissa
family-names: Pearson
- given-names: Suzanne
family-names: Pierce
email: spierce@tacc.utexas.edu
affiliation: Texas Advanced Computing Center
orcid: 'https://orcid.org/0000-0002-3050-1987'
repository-code: >-
https://github.com/In-For-Disaster-Analytics/Cookbook-Tutorial-Template
license: Apache-1.0
GitHub Events
Total
- Issues event: 2
- Push event: 20
- Pull request event: 1
- Create event: 1
Last Year
- Issues event: 2
- Push event: 20
- Pull request event: 1
- Create event: 1
Dependencies
- actions/checkout v4 composite
- docker/build-push-action v5 composite
- docker/login-action 65b78e6e13532edd9afa3aa52ac7964289d1a9c1 composite
- docker/metadata-action v4 composite
- docker/setup-buildx-action v3 composite
- nvidia/cuda 12.3.0-runtime-ubuntu22.04 build