Editing CommunityData:TACC (section)

=== Create a python virtual environment for your project ===

{{note}} A good workflow is to develop code locally and then test it on the HPC. This helps because: (1) You can use your favored editor locally instead of working with limited tools like Jupyter, terminal editors, or working with a GUI over the network. (2) It uses resources to use HPC nodes. (3) Particularly with the H100 nodes on TACC, you might have to wait (sometimes over a day) for an available node. <code>uv</code> is useful because it creates a `pyproject.toml` and `uv.lock` file. If you check these into git and sync them to the HPC, `uv` will make sure that the Python project on your laptop and the HPC are using the same package versions.

{{note}} Given the filesystem situation described above, you will normally work with large data objects on the <code>$SCRATCH</code> filesystem, and copy your datasets and results to <code>$CORRAL</code>. Make a new directory (i.e., using <code>mkdir</code>) to use for the following steps. 

You can create a virtual environment using <code>uv</code> with this command:

<code>uv init</code>

Recommend: add `uv` as a dev package to the virtual environment and then sourcing it. 

<code>uv add --dev uv</code>

<code>source .venv/bin/activate</code>.