Skip to content

Feature head mapping - #45

Open
AbhirupaGhosh wants to merge 7 commits into
mainfrom
feature_head_mapping
Open

Feature head mapping#45
AbhirupaGhosh wants to merge 7 commits into
mainfrom
feature_head_mapping

Conversation

@AbhirupaGhosh

Copy link
Copy Markdown
Contributor

Description

Introduce feature-dyad mapping in the format of two columns, where dyad is protein|gene combination.

What kind of change(s) are included?

  • Feature (adds or updates new capabilities)
  • Bug fix (fixes an issue).
  • Enhancement (adds functionality).
  • Breaking change (these changes would cause existing functionality to not work as expected).

Checklist

Please ensure that all boxes are checked before indicating that this pull request is ready for review.

  • I have read and followed the CONTRIBUTING.md guidelines.
  • I have searched for existing content to ensure this is not a duplicate.
  • I have performed a self-review of these additions (including spelling, grammar, and related).
  • I have added comments to my code to help provide understanding.
  • I have added a test which covers the code changes found within this PR.
  • I have deleted all non-relevant text in this pull request template.
  • Reviewer assignment: Tag a relevant team member to review and approve the changes.

epbrennerand others added 5 commits August 12, 2026 16:05
1. Moved many common and utility functions to helpers.R
2. Added new manifest feature, logging all steps of workflow
- Manifest is also used to identify which HMMER databases have run on a bug.
- Adds extensive data provenance logging + moves databases to R user cache.
3. Removes InterProScan entirely
4. Adds Abhirupa's HMMER functionality to data_processing.R, removed runHMMER.R
5. Replaced "domain" tables/features with Pfam/COG/AMRFinder/DefenseCas
6. Added jsonlite to Imports
7. stuff
Co-Authored-By: Abhirupa Ghosh <100681585+AbhirupaGhosh@users.noreply.github.com>
Introduce new function to map features to head instead of protein clusters and change the approach of reading from parquet_duckdb to only parquets.
Some reshuffling but mostly just adding support for manifest and modifying the way parameters are handled to account for manifest detection. Should be able to dynamically add databases through this, but accounting for different column names in those new DBs will take additional effort.
epbrenner
epbrenner previously approved these changes Aug 19, 2026

@epbrennerepbrenner left a comment

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.

Works for me! But I also added the manifest stuff to this, so somebody else needs to approve before merging.

@AbhirupaGhosh
AbhirupaGhosh dismissed epbrenner’s stale reviewAugust 19, 2026 21:49

The merge-base changed after approval.

@AbhirupaGhosh

Copy link
Copy Markdown
ContributorAuthor

The integration of manifest JSON in the buildDyadFeatureMap() works as usual.

This PR can be merged.

epbrenner
epbrenner previously approved these changes Aug 20, 2026

@epbrennerepbrenner left a comment

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 still think this PR is cool. I still also think it could use one more review.

@AbhirupaGhosh
AbhirupaGhosh dismissed epbrenner’s stale reviewAugust 20, 2026 18:25

The merge-base changed after approval.

…database name column for HMMER generated matrices.
Sign up for freeto 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.

2 participants

@AbhirupaGhosh@epbrenner