Vyas Ramasubramani

Presence of hidden files breaks editable installs

3

Git supports nested `.gitignore` files. The presence of such a file inside the project's source currently breaks editable installs with the following traceback: ``` ... File "scikit_build_core/build/__init__.py", line 54, in...

Use rapids-build-backend.

3

## Description This PR uses `rapids-build-backend` to simplify wheel builds and reduce the complexity of various CI/build scripts. See also: - https://github.com/rapidsai/rapids-build-backend - https://github.com/rapidsai/build-planning/issues/31 ## Checklist - [x] I am...

Support modification of the subprocess environment created when groups fork to execute operations

1

### Feature description Operations that require forking, either via an explicit `fork` directive or using any other directives that trigger forking like `nranks` (via MPI) or `executable`, end up executing...

Establish clear flow schema

5

This issue is part of glotzerlab/signac#527 but requires a more focused thread. signac-flow currently stores a number of pieces of internal data, such as bundles, submission status, and configuration information...

Simplify environment detection

6

@bdice @mikemhenry @csadorf following up on #498, I think we should consider removing scheduler-based environment detection entirely. @bdice correct me if I've misunderstood the problem, but #498 came up because...

When requesting more GPUs than are available on a single node during submission, signac-flow needs to consider how the CPU tasks are distributed. It doesn't make sense to allocate all...

Speed up parameter formatting in status

4

### Feature description I have a somewhat large signac project (~500) jobs with some complicated conditions. I've profiled and cleaned up the conditions, but I was still finding the status...

Improve documentation of accounts

2

### Feature description Right now submission on a specific environment uses a template filter to pull the account from the environment's namespace in the config. This behavior is undocumented, but...

By default, we perform thread-parallel execution of status fetching operations, but it's not clear that this mode is always desirable relative to serial execution since it only accelerates highly I/O...

This can be deferred, I just didn't know what to do if the user requests to show state point parameters and aggregates exist. It might make sense to show common...