Bradley Dice

@glotzerlab/signac-committers Other suggestions for implementation are welcome. @ac-optimus Since this is fairly complicated, I would like to see a small proposal for the work to be done (which parts of...

Yes, refactoring directives seems like a good place to start. (To clarify, the use of the word "aggregation" here in the context of determining resource requests over a set of...

I strongly favor (A). We want to treat hooks like a "plugin system" for which we provide a handful of nice plugins, rather than treating each of the hooks provided...

Adding a permalink to this code section on the current commit of `master`, for posterity and convenience: https://github.com/glotzerlab/signac-flow/blob/215b252bbda798d2fcb9f0b44917c4fd70e996c5/flow/project.py#L1872-L1902

This code is also the only place that `_to_hashable` is used (see PR #384). It seems like this portion of the code could use a thorough refactoring. I have a...

@vyasr Generally looks good to me, and I think it's close enough that we can begin work on this set of proposals. ------- ## Comments on Concrete Proposals My understanding...

> However, accounts are a bit different from our other config variables: they're really submission directives masquerading as config data so that we can hide them in .signacrc (and share...

I know of several users who rely on the default scheduler detection for systems without templates. I think it is a very helpful and important feature for ease of use....

Discussed with @csadorf offline - this issue is different than the one resolved by #209. This suggested feature is about automatic execution of dependent operations (from the graph detected by...

I haven't investigated RADICAL-Pilot very deeply, so I don't have much info to add there. - QCFractal (http://docs.qcarchive.molssi.org/projects/qcfractal/en/latest/) has many similar features, though it is currently built for mostly quantum...