Skip to content
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

Evaluate & add entry points #118

Open
Tracked by #121
GwennyGit opened this issue Apr 9, 2024 · 0 comments
Open
Tracked by #121

Evaluate & add entry points #118

GwennyGit opened this issue Apr 9, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed refactoring changes in the code functionality

Comments

@GwennyGit
Copy link
Collaborator

GwennyGit commented Apr 9, 2024

Gather & evaluate entry points

Module Submodule Possible entry points Notes Status1
analysis comparison Annotation/SBO report? 🟥
  core_pan generate_core_pan
compare_to_core_pan
1. setup, 2. analyse 🟩; untested
  growth growth_analysis
test_auxotrophies
test_growth_with_source
model_minimal_medium
Sum all test modules to one entry point up? - done 4 🟩 , partially not tested
  investigate A new function as entry point? 🟫
classes egcs One call with flags 🟩
  medium Are there any feasible/necessary entry points? 🟫
  reports got 'em covered 🟩
curation db_access compare_to_modelseed Make wider comparable with more namespaces? 🟥
  biomass check_normalise_biomass 🟩
  charges correct_charges_modelseed correct_charges_from_database $\rightarrow$ Extension? As a replacement for correct_charges_modelseed? 🟦 / 🟩
  curate Which function(s) to add as entry point(s)? 🟫
  gapfill gapfill one call 🟩
  pathways kegg_pathways in sth. like 'refine' 🟩
  polish check_direction
polish
One function for add_gp_ids_from_... as an entry point?
polish_annotations + change_all_qualifiers as one entry point/separate ones?
🟥
utility cvterms None $\textcolor{magenta}{\text{Possible for future release}}$ 🟫
  databases initialise_database 🟩 2
  io save_user_input put together with other configs? 🟫 -> moved to SPECIMEN (draeger-lab/SPECIMEN/issues/8)
  set_up download_config one for all or one for each 🟥 what about rg config? / 🟩 media config

What to do about data & examples?

Footnotes

  1. 🟥 = under discussion; 🟦 = needs to be implemented; 🟩 = implemented; 🟫 = will not be implemented

  2. for further information and TODOs/IDEAs, see comments in code

@GwennyGit GwennyGit added enhancement New feature or request help wanted Extra attention is needed refactoring changes in the code functionality labels Apr 9, 2024
GwennyGit added a commit that referenced this issue Apr 16, 2024
GwennyGit added a commit that referenced this issue Apr 17, 2024
cb-Hades added a commit that referenced this issue Apr 19, 2024
cb-Hades added a commit that referenced this issue Apr 19, 2024
cb-Hades added a commit that referenced this issue Apr 22, 2024
cb-Hades added a commit that referenced this issue Apr 22, 2024
cb-Hades added a commit that referenced this issue May 23, 2024
cb-Hades added a commit that referenced this issue May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed refactoring changes in the code functionality
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants