Skip to content

Add datatype for LexicMap index #20586

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

Smeds
Copy link

@Smeds Smeds commented Jun 30, 2025

LexicMap

LexicMap is a nucleotide sequence alignment tool for efficiently querying gene, plasmid, viral, or long-read sequences (>100 bp) against up to millions of prokaryotic genomes.

To perform queries, an index must first be created. The index is stored as a folder structure containing metadata and binary data files.

Example Index Directory Structure

lexicmap_index/
├── genomes.chunks.bin
├── genomes.map.bin
├── info.xml
├── masks.bin
├── genomes/
│ ├── batch_0000/
│ │ ├── genomes.bin
│ │ └── genomes.bin.idx
│ └── batch_NNNN/
│ ├── genomes.bin
│ └── genomes.bin.idx
└── seeds/
├── chunk_000.bin
├── chunk_000.bin.idx
...
├── chunk_NNN.bin
└── chunk_NNN.bin.idx

How to test the changes?

(Select all options that apply)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

@Smeds
Copy link
Author

Smeds commented Jun 30, 2025

this new datatype will be used by tool lexicmap, pull-request 7106

@ahmedhamidawan ahmedhamidawan changed the title datatype added for LexicMap index Add datatype for LexicMap index Jun 30, 2025
@bernt-matthias
Copy link
Contributor

You can target 25.0

@Smeds
Copy link
Author

Smeds commented Jul 9, 2025

You can target 25.0

I have changed the tool to have profile version set to 25.1

@bernt-matthias
Copy link
Contributor

You can target 25.0

I have changed the tool to have profile version set to 25.1

Then the tool won't be usable until 25.1 is released and installed.. Guess this might need approx 6 month.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants