Eric Coissac 61e346658e Refactor jjpush workflow and enhance release notes generation
Split the jjpush target into multiple sub-targets (jjpush-describe, jjpush-bump, jjpush-push, jjpush-tag) for better modularity and control.

Enhance release notes generation by:
- Using git log with full commit messages instead of GitHub API for pre-release mode
- Adding robust JSON parsing with fallbacks for release notes
- Including detailed installation instructions in release notes
- Supporting both pre-release and published release modes

Update release_notes.sh to handle pre-release mode, improve commit message fetching, and add installation section to release notes.

Add .PHONY declarations for new sub-targets.
2026-03-10 11:09:19 +01:00
2024-06-07 09:04:37 +02:00
2023-12-05 15:28:29 +01:00
2026-02-20 11:40:43 +01:00
2023-02-02 23:47:22 +01:00
2025-06-04 09:48:10 +02:00
2023-02-02 23:36:13 +01:00
2022-01-14 15:22:10 +01:00
2025-04-10 15:16:36 +02:00
2025-04-10 15:16:36 +02:00
2026-02-20 11:40:43 +01:00

obitools V4

OBITools V4 is the new version of OBITools. They are closer to OBITools2 than to OBITools3. They are implemented in GO and are tens of times faster than OBITools2.

The git for OBITools4 is available at :

https://github.com/metabarcoding/obitools4

Installing OBITools V4

An installation script that compiles the new OBITools on your Unix-like system is available online. The easiest way to run it is to copy and paste the following command into your terminal

curl -L https://raw.githubusercontent.com/metabarcoding/obitools4/master/install_obitools.sh | bash

By default, the script installs the latest version of OBITools commands and other associated files into the /usr/local directory.

Installation Options

The installation script offers several options:

-l, --list List all available versions and exit.

-v, --version Install a specific version (e.g., -v 4.4.3). By default, the latest version is installed.

-i, --install-dir Directory where obitools are installed (as example use /usr/local not /usr/local/bin).

-p, --obitools-prefix Prefix added to the obitools command names if you want to have several versions of obitools at the same time on your system (as example -p g will produce gobigrep command instead of obigrep).

Examples

List all available versions:

curl -L https://raw.githubusercontent.com/metabarcoding/obitools4/master/install_obitools.sh | bash -s -- --list

Install a specific version:

curl -L https://raw.githubusercontent.com/metabarcoding/obitools4/master/install_obitools.sh | bash -s -- --version 4.4.3

Install in a custom directory with command prefix:

curl -L https://raw.githubusercontent.com/metabarcoding/obitools4/master/install_obitools.sh | \
      bash -s -- --install-dir test_install --obitools-prefix k

In this last example, the binaries will be installed in the test_install directory and all command names will be prefixed with the letter k. Thus, obigrep will be named kobigrep.

Note on Version Compatibility

The names of the commands in the new OBITools4 are mostly identical to those in OBITools2. Therefore, installing the new OBITools may hide or delete the old ones. If you want both versions to be available on your system, use the --install-dir and --obitools-prefix options as shown above.

Continuing the analysis...

Before with OBITools2 to continue the analysis, obitab was used as last command to produce a tab delimited file that was loadable in R or in any spreadsheet. The generated file was huge and required to load the full dataset in memory to be produced. Hereby OBITools4 proposes to substitute the obitab usage by the ROBIFastRead R module.

Description
No description provided
Readme 190 MiB
Languages
Go 75%
HTML 11.4%
Shell 5.6%
C 4%
JavaScript 3.3%
Other 0.6%