This repository provides a Common Workflow Language (CWL) tool for running the jb2export program. The tool is packaged in a Docker container, allowing it to run on any system with Docker or Singularity installed.
To use this tool, you must have the following software installed on your system:
- CWL tool
- Docker OR Singularity OR Apptainer
To install and run the tool, follow these steps:
-
Clone this repository to your local machine.
-
Install Docker, if you haven't already done so.
-
(optional) Build the Docker image by running the following command from the root of the repository:
docker build -f docker/Dockerfile -t jb2export-docker-cwl .OR pull from the built container.
docker pull ghcr.io/bwbioinfo/jb2export-docker-cwl:latestNote: this is only needed if you wish to access the container commands directly via docker.
-
Run the CWL tool by running the following command from the root of the repository:
cwl-runner jb2export.cwl jb2export.ymlOR
cwl-runner --singularity jb2export.cwl jb2export.ymlThis will run the jb2export software on the input sequence specified in the
jb2export.ymlfile.
To use the tool, you will need to create a YAML file specifying the input sequence and any other parameters you wish to specify. An example YAML file is provided in the example directory of this repository.
The jb2export.cwl file is the main workflow file that describes the steps of the jb2export analysis. The jb2export.yaml file is an example input file that specifies the input and any other options you wish to specify. The jb2export.cwl file includes the docker specification. You can also use Singularity via the cwl-runner option --singularity
The output of the analysis will be written to a directory named output in the current working directory.
If you wish to contribute to this project, please follow the standard GitHub workflow:
- Fork the repository
- Create a new branch for your changes
- Make your changes and commit them
- Push your changes to your fork
- Submit a pull request to this repository
This project is licensed under the MIT License.
If you have any questions or feedback, please contact the author via GitHub.