Skip to content

Compleasm: use busco_database_options for lineages instead of hardcoded ones#7915

Open
Delphine-L wants to merge 2 commits intogalaxyproject:mainfrom
Delphine-L:compleasm
Open

Compleasm: use busco_database_options for lineages instead of hardcoded ones#7915
Delphine-L wants to merge 2 commits intogalaxyproject:mainfrom
Delphine-L:compleasm

Conversation

@Delphine-L
Copy link
Copy Markdown
Contributor

@Delphine-L Delphine-L commented Apr 21, 2026

FOR CONTRIBUTOR:

  • I have read the CONTRIBUTING.md document and this tool is appropriate for the tools-iuc repo.
  • License permits unrestricted use (educational + commercial)
  • This PR adds a new tool or tool collection
  • This PR updates an existing tool or tool collection
  • This PR does something else (explain below)

There are two labels that allow to ignore specific (false positive) tool linter errors:

  • skip-version-check: Use it if only a subset of the tools has been updated in a suite.
  • skip-url-check: Use it if github CI sees 403 errors, but the URLs work.

@SaimMomin12 SaimMomin12 enabled auto-merge (squash) April 21, 2026 16:40
@SaimMomin12 SaimMomin12 disabled auto-merge April 21, 2026 19:17
@SaimMomin12
Copy link
Copy Markdown
Contributor

@Delphine-L could you please adapt the tests according to the recent modifications?

Copy link
Copy Markdown
Contributor

@bernt-matthias bernt-matthias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ln -s '${busco_database.fields.path}/lineages/${lineage_dataset}/' 'galaxy_db/${lineage_dataset}' &&
## Create a compleasm-specific empty file to avoid redownloading the lineage data (https://github.com/huangnengCSU/compleasm/blob/0.2.6/compleasm.py#L165)
touch 'galaxy_db/${lineage_dataset}.done' &&
echo ${__HERE__} &&
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not think that this part is needed. Instead you need to add an entry to the options data table test file.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean the whole block and the hidden test variable

@Delphine-L
Copy link
Copy Markdown
Contributor Author

@SaimMomin12 I am not sure how to write tests for data tables. busco doesn't use them . Could you take a look ?

@bernt-matthias
Copy link
Copy Markdown
Contributor

For using the new data table you will need to add an entry for the data table in tool_data_table_conf.xml.sample. This will refer to a sample sample loc in the tool-data folder. So you will also need to add this sample file (basically empty - only explaining comments).

You can copy from here:

For the tests you need:

  • an entry in the tool_data_table_conf.xml.test. This refers to a loc file in the test-data directory.
  • the loc file in the test data directory which should contain the two entries needed for your tests

I guess you can draw inspiration from the busco tool as well.

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.

3 participants