Docs: add example conda environment and installation troubleshooting

[aymaneVXx]

This PR improves the installation experience for Evo 2 by:

• Adding an example environment.yml with a reproducible conda setup (Python 3.12, CUDA 12.1, PyTorch 2.5.1, Transformer Engine, FlashAttention, Vortex).
• Updating the README with:
  • an "Example conda environment" section, and
  • a "Troubleshooting (installation)" section that covers common errors involving transformer_engine, vortex, and CUDA/NVRTC library issues.

These changes are intended to help new users create a working environment more easily and reduce repeated installation-related questions in existing GitHub issues.

[gemini-code-assist]

Summary of Changes

Hello @aymaneVXx, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the installation experience for Evo 2 by introducing a standardized and reproducible conda environment configuration. It also provides clear, actionable troubleshooting guidance within the documentation to help users resolve common setup issues, aiming to reduce friction for new users and minimize recurring support questions.

Highlights

• Conda Environment Example: An example environment.yml file has been added to provide a reproducible conda setup for Evo 2, pinning specific versions of Python, CUDA, PyTorch, Transformer Engine, FlashAttention, and Vortex.
• README Update: Example Conda Environment: The README.md now includes a new section detailing how to use the provided environment.yml to create and activate the recommended conda environment.
• README Update: Installation Troubleshooting: A comprehensive 'Troubleshooting (installation)' section has been added to the README.md, addressing common errors related to transformer_engine, vortex, and CUDA/NVRTC library issues, along with suggested fixes.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request is a great addition to improve the user installation experience. I've found a couple of areas for improvement. In environment.yml, the flash-attn package should be installed via pip to ensure the correct version is used, as it's not available on the specified conda channels. In README.md, the new troubleshooting section has some markdown formatting issues that I've suggested fixes for to improve readability. Overall, these changes will be very helpful for new users.