Add micromamba instructions to loc file install docs #86
Conversation
|
@mikemhenry please do ping me when it's ready to review! |
|
@IAlibay ready for review! |
docs/source/installation.rst
Outdated
| $ micromamba create -n openfe --file openfe-1.0.1-conda-lock.yml | ||
| $ micromamba activate openfe | ||
|
|
||
| If ``micromamba`` is not available, ``conda`` or ``mamba`` may be used after installing ``conda-lock``. |
There was a problem hiding this comment.
This section is a bit confusing - do you think it would be better if we broke this into two sections? I.e. one "conda-lock with micromambaandclassical conda-lock" or something like that?
That way if it doesn't work for one we tell folks to look at the other section.
There was a problem hiding this comment.
Yes I will re-write it like that, sometimes I don't want to kill my darlings -- but an more thorough rewrite makes more sense
Co-authored-by: Irfan Alibay <IAlibay@users.noreply.github.com>
When using https for anaconda channels, it prints them twice: conda-forge/linux-64 Using cache conda-forge/noarch Using cache conda-forge/linux-64 Using cache conda-forge/noarch Using cache Instead if you use `- conda-forge` it prints them once conda-forge/linux-64 Using cache conda-forge/noarch Using cache IDK why
|
@IAlibay ready for re-review! I think the section is more clear, I also added a link to testing the installation at the end of each section. I also made the or bold to make it clear if you create an env with a lock file, you don't need to also use the single file installer. |
Input submission checklist
input_structures/prepared_structures/<set_name>/<system_name>For each submitted directory:
PREPARATION_DETAILS.mdfileprotein.pdbcofactors.sdfligands.sdfand removed any duplicate binding modes or protonation states, keeping the more favorable stateSummary of changes
Licensing agreement