Add: deepchopper #51460
Add: deepchopper #51460
Conversation
|
@mencian, Thanks for cleaning the code, and have a good one! |
recipes/deepchopper/meta.yaml
Outdated
| - setuptools | ||
| run: | ||
| - python | ||
| - torch >=2.1.0 |
There was a problem hiding this comment.
The ARM64 builds fail due to:
11:23:33 BIOCONDA INFO (OUT) Encountered problems while solving:
11:23:33 BIOCONDA INFO (OUT) - nothing provides requested torch >=2.1.0
But https://anaconda.org/search?q=torch does not list such package in conda-forge and/or bioconda channels at all.
I guess the same error will be reported for x86_64 once the CI issue is solved.
Did you mean https://anaconda.org/conda-forge/pytorch ?
There was a problem hiding this comment.
@martin-g, thank you for your excellent help! I just realize I made a mistake. The PyTorch package names are different for conda and pip:
In conda: 'pytorch'
In pip: 'torch'"
I've found two good PyTorch options:
The conda-forge version (conda-forge/pytorch) which works great for my needs
The official PyTorch channel (pytorch/pytorch) which provides the latest releases
Both are available through Anaconda, and I can work with either option.
Again, Thanks for your help!
|
Caution Review failedThe pull request is closed. 📝 WalkthroughWalkthroughThis pull request introduces two key components for the "deepchopper" package: a new The Possibly related PRs
Suggested labels
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
@mencian, appreciate your big help again! Have a good one. |
|
Anytime~ |
Describe your pull request here
Language models identify chimeric artificial reads in NanoPore direct-RNA sequencing data.
Please read the guidelines for Bioconda recipes before opening a pull request (PR).
General instructions
@BiocondaBot please add labelcommand.@bioconda/corein a comment.Instructions for avoiding API, ABI, and CLI breakage issues
Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify
run_exports(see here for the rationale and comprehensive explanation).Add a
run_exportssection like this:with
...being one of:{{ pin_subpackage("myrecipe", max_pin="x") }}{{ pin_subpackage("myrecipe", max_pin="x.x") }}{{ pin_subpackage("myrecipe", max_pin="x.x") }}(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin="x.x.x") }}(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin=None) }}while replacing
"myrecipe"with eithernameif aname|lowervariable is defined in your recipe or with the lowercase name of the package in quotes.Bot commands for PR management
Please use the following BiocondaBot commands:
Everyone has access to the following BiocondaBot commands, which can be given in a comment:
@BiocondaBot please update@BiocondaBot please add labelplease review & mergelabel.@BiocondaBot please fetch artifactsYou can use this to test packages locally.
Note that the
@BiocondaBot please mergecommand is now depreciated. Please just squash and merge instead.Also, the bot watches for comments from non-members that include
@bioconda/<team>and will automatically re-post them to notify the addressed<team>.