Skip to content

Fix relative path management to find pangenome.h5 file#54

Open
jpjarnoux wants to merge 1 commit intodevfrom
bugfix/53-unable-to-locate-pangenome
Open

Fix relative path management to find pangenome.h5 file#54
jpjarnoux wants to merge 1 commit intodevfrom
bugfix/53-unable-to-locate-pangenome

Conversation

@jpjarnoux
Copy link
Member

The current behavior is to use the absolute path or the working directory relative path to find pangenome file. This is not the expected behavior describe in the documentation.

Example:

  • file tree
    ├── pangenome1.h5
    ├── pangenome2.h5
    ├── pangenomes
    │   ├── pangenome3.h5
    │   └── pangenome4.h5
    └── pangenomes.tsv

  • pangenomes.tsv
    pangenome1 /home/user/absolute/path/pangenome1.h5
    pangenome2 pangenome2.h5
    pangenome3 pangenomes/pangenome3.h5
    pangenome4 /home/user/absolute/path/pangenome4.h5

This work if panorama is executed where pangenomes.tsv exist.

I Enhanced path resolution by adding the resolve_path function to handle both absolute and relative paths robustly.
I Updated check_tsv_sanity to utilize this function for improved error handling and path validation.

Enhanced path resolution by adding the `resolve_path` function to handle both absolute and relative paths robustly. Updated `check_tsv_sanity` to utilize this function for improved error handling and path validation.
@jpjarnoux jpjarnoux linked an issue Feb 16, 2026 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unable to locate pangenome

1 participant

Comments