David L. Dotson

Thanks @jchodera! I think the rough ideas here are sound, and we'll use this issue as the basis for building out a user-facing CLI for working with submitted networks at...

Proposed API point: ``` def get_archival_extract( network: ScopedKey, metadata: Dict[str, Any], ) -> AlchemicalArchive: """ Tuple[AlchemicalNetwork, Dict[str, List[ProtocolDAGResult]], Dict[str, Any]] """ ... ``` where an `AlchemicalArchive` is a new data...

This has been partially addressed by #41/#53. We want to extend that approach to support wildcards or regexes next in #42. #43 will address more granular permissioning.

Thanks for this @JenkeScheen! I agree that this would work well as a relatively simple `Strategy` that we could implement to make more meaningful forward progress on a network. I'd...

This issue would be partially addressed by a solution to #237. This would allow users such as @JenkeScheen to reduce the number of active `AlchemicalNetwork`s by marking those no longer...

@JenkeScheen were you able to make use of this feature in `asap-alchemy`? Documentation on how to use network state is in the User Guide here: https://docs.alchemiscale.org/en/latest/user_guide.html#marking-alchemicalnetworks-as-inactive-deleted-or-invalid

Excellent, thank you!

As a mitigation, we could for now add detection of the common source of this issue (`Transformation` of the same `ChemicalSystem` as `stateA` and `stateB`) in the state store codepath...

Should be addressed by resolution of #144.

Speaking with @ianmkenney, we propose: - adding the ability for a server administrator to specify the list of modules that versions should be reported for as configuration items in the...