You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current instructions explain how to install WSIMOD using conda directly from the GitHub repo. There's nothing wrong with that, but it will be more convenient to deploy the tool to a common repository, like PyPI, allowing the installation of WSIMOD in exactly the same way but also enforcing a versioning, which is necessary for a professional tool.
As much as we would like to to this soon, there are several issues that need solving before we are confident we are deploying a robust tool with a clear documentation (including well documented API documentation):
@barneydobson , this is not urgent - in the sense that it does not affect other work that we need to do - but I think it will be useful to have it done as soon as possible and release a new version of the software, deployed in PyPI, so any future development follows the same pattern.
Are you happy for us to create a new release (0.4.0, if we continue from the last one) and move on from there?
@barneydobson , it seems this will take a while. We feel the tool needs a bit more work before we can deploy it with confidence in pypi. See updated description.
@liuly12 , this should not affect the DAFNI side of the project.
The current instructions explain how to install WSIMOD using
conda
directly from the GitHub repo. There's nothing wrong with that, but it will be more convenient to deploy the tool to a common repository, like PyPI, allowing the installation of WSIMOD in exactly the same way but also enforcing a versioning, which is necessary for a professional tool.I'd suggest a something similar to what we implemented in MUSE but triggered by releases, as it is done in Health-GPS.
Documentation needs updating accordingly.
Update
As much as we would like to to this soon, there are several issues that need solving before we are confident we are deploying a robust tool with a clear documentation (including well documented API documentation):
The text was updated successfully, but these errors were encountered: