Corwin Kerr

A related use is tracking scheduler job IDs to track down errors more easily. It might be a separate issue. There are two steps in this translation: scheduler ID -->...

Do schedulers return job ID? SLURM: Officially no https://slurm.schedmd.com/sbatch.html (find "RETURN VALUE" section). We can definitely get job ID after creating from `squeue`, but I don't know if that number...

Some notes from discussion with @csadorf and @bdice yesterday afternoon: - Not all schedulers return scheduler ID, just "success" status - I learned that we store bundle information in `project_root/.bundles/project_name/bundle/[bundle_IDs]`...

Related issue discussed with @yuanzhou0827, you can't specify the partition in the config settings. Not sure if that would be helpful once you're on a certain cluster

Thank you! I was always confused by differences in how flow does things and how user guides for SLURM etc describe things...processes, threads, ranks, oh my! > Alternately, we could...

It's pulling the information from [OperationRegister](https://github.com/glotzerlab/signac-flow/blob/master/flow/project.py#L1415), but I'm not sure why.

@vale981, PRs welcome over at https://github.com/orgzly-revived/orgzly-android-revived!

I see PyTables has a PR for fixing this, so I vote we wait a couple weeks and check back

The tests already have pandas and tables in a separate list `requirements-test-optional.txt`, and we see that only the "newest" tests fail. "Minimal" and "oldest" tests work, but those do not...