Arjun Verma

Results 51 issues of Arjun Verma

Currently we run all the tests with `pybamm[all]` with all optional dependencies installed on CI but as we also maintain `pybamm` without optional dependencies it is necessary to cover that...

difficulty: easy
priority: medium
CI/CD

### Description [uv](https://github.com/astral-sh/uv) is a quick Python package installer and resolver, made with Rust. It's meant to work just like pip and pip-tools, but faster. ### Motivation The introduction of...

feature
difficulty: easy
priority: medium

This would potentially cut down an external system dependency `conda` & would reduce the inconsistency of environments across different OS for IDAKLU solver images.

difficulty: easy
priority: medium

Currently we build and push 5 variants of Docker Images regularly i.e. `latest`, `jax`, `odes`, `idaklu` & `all`. The idea behind this issue is to have a single standard image...

difficulty: easy
priority: medium

# Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change....

Enabling lazy loading of submodules should potentially make PyBaMM import faster. See also: https://scientific-python.org/specs/spec-0001/ _Originally posted by @agriyakhetarpal in https://github.com/pybamm-team/PyBaMM/issues/3475#issuecomment-1786894302_

difficulty: medium
priority: medium

# Description Push Docker images on releases, starting from either `23.9` or `24.1` before the `24.1rc0` release ## Type of change Please add a line in the relevant section of...

# Description Been proposed in #3866 ## Type of change Please add a line in the relevant section of [CHANGELOG.md](https://github.com/pybamm-team/PyBaMM/blob/develop/CHANGELOG.md) to document the change (include PR #) - note reverse...

This PR aims to give user the total control with `pip install ragna` i.e. which will correspond to current `ragna[all]` & also proposes a proof of concept for `ragna-base` which...

### Context I am encountering issues connecting to the Kubernetes ingress host (172.18.1.100:80) after successfully deploying Nebari locally using the "kind" Kubernetes setup. This issue occurs despite the Terraform apply...

needs: triage 🚦