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

Enhance availability of refineGEMs #85

Open
2 tasks
GwennyGit opened this issue May 4, 2023 · 4 comments
Open
2 tasks

Enhance availability of refineGEMs #85

GwennyGit opened this issue May 4, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@GwennyGit
Copy link
Collaborator

GwennyGit commented May 4, 2023

To enhance the availability of the whole refineGEMs package I would suggest the following options:

@GwennyGit GwennyGit added the enhancement New feature or request label May 4, 2023
famosab added a commit that referenced this issue May 9, 2023
famosab added a commit that referenced this issue May 9, 2023
famosab added a commit that referenced this issue May 9, 2023
GwennyGit added a commit that referenced this issue Jul 6, 2023
GwennyGit added a commit that referenced this issue Jul 10, 2023
GwennyGit added a commit that referenced this issue Jul 13, 2023
Needed to change the workflow to only be triggered via workflow_dispatch as the pushing to test-pypi did not work and as it is safer to trigger it manually then automatically.
GwennyGit added a commit that referenced this issue Jul 13, 2023
Needed to remove the old version as the changed file was renamed
GwennyGit added a commit that referenced this issue Aug 18, 2023
To make functions accessing the database functional within user scripts I had to move the files into the package folder.
@GwennyGit
Copy link
Collaborator Author

For task 1, another idea would be to split the tool into different entry points. One for model investigation, one for model refinement and one for model curation.

How to achieve?

  • Generate four 'main' modules/ command line names: data, investigate, refine and curate
  • Extract code from io and main for the relevant modules per new 'main' module (see table)
  • Add entry points to the setup.py
'Main' module/Command line name Relevant modules Description
data databases Handles database input/output & initialisation
investigate comparison, growth, investigate, gapfill.gap_analysis Handles model comparison, growth simulation & other types of model investigation
refine biomass, charges, modelseed, pathways, polish, sboann Handles all possible refinement techniques implemented in refineGEMs
curate curate, gapfill.gapfill_model Handles the curation implementations of refineGEMs

@GwennyGit
Copy link
Collaborator Author

GwennyGit commented Aug 21, 2023

The setup.py should be replaced by a setup.cfg as the setup.py file is legacy and might get deprecated. A possible setup.cfg, already including the setup for the possible entry points, was generated and uploaded to the branch structure_update.

As with refineGEMs 1.4.0 the pyproject.toml file was adjusted so that the complete install is only handled by the pyproject.toml. This deprecates the setup.cfg which is now removed with the commit Removed no longer needed setup.cfg. The already existing entry points were moved as comments to the pyproject.toml file with the commit Added entry points as comments to pyproject.toml and need to be tested and adjusted before use.

GwennyGit added a commit that referenced this issue Aug 21, 2023
To make functions accessing the database functional within user scripts I had to move the files into the package folder.
GwennyGit added a commit that referenced this issue Aug 21, 2023
To make functions accessing the database functional within user scripts I had to move the files into the package folder.
GwennyGit added a commit that referenced this issue Aug 21, 2023
To make functions accessing the database functional within user scripts I had to move the files into the package folder.
@GwennyGit
Copy link
Collaborator Author

All commits from the last comment to this comment are the result of my attempt to rebase these commits from dev to another branch. However, this did not work and, thus, I will cherry-pick the according commits to the other branch. This will likely add the same commits again in this issue after this comment.

GwennyGit added a commit that referenced this issue Aug 21, 2023
To make functions accessing the database functional within user scripts I had to move the files into the package folder.
GwennyGit added a commit that referenced this issue Sep 18, 2023
I broke the setup of Pipfile & Pipfile.lock and I found no solution to fix or update both files. Moreover, I think these files are obsolete and unneccesary to be distributed. Thus, I removed the files from the package completely.
f3rryman added a commit that referenced this issue Sep 27, 2023
GwennyGit added a commit that referenced this issue Nov 14, 2023
@cb-Hades
Copy link
Collaborator

cb-Hades commented Jan 10, 2024

Currently, refineGEMs works for python 3.10 and 3.9.
Release 2.0.0 should work under 3.10 and 3.11

  • 3.10
  • 3.11
  • 3.12
  • 3.13

cb-Hades added a commit that referenced this issue Feb 8, 2024
- added ideas and possible new code for io #85, #44 and investigate to CB_under_construction
- bit of restructering in io and investigate
- bit of Specimen integration in new code block CB_under_construction #99
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants