Closed richardjgowers closed 10 months ago
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
a426dce
) 99.21% compared to head (88c3efb
) 99.21%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Hello @richardjgowers! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
gufe/tests/test_protocol.py
:Line 115:75: E252 missing whitespace around parameter equals Line 115:76: E252 missing whitespace around parameter equals Line 115:80: E501 line too long (80 > 79 characters) Line 175:75: E252 missing whitespace around parameter equals Line 175:76: E252 missing whitespace around parameter equals Line 175:80: E501 line too long (80 > 79 characters) Line 516:80: E501 line too long (86 > 79 characters)
gufe/tests/test_protocoldag.py
:Line 56:80: E501 line too long (89 > 79 characters) Line 58:80: E501 line too long (90 > 79 characters)
gufe/transformations/transformation.py
:Line 31:80: E501 line too long (82 > 79 characters) Line 71:80: E501 line too long (83 > 79 characters)
@dwhswenson I think I'm going the other way, I'll make the mapping
argument take (edit: either a list of mappings or) a single instance (since this is currently all cases?) and not have to explain that technically we've thought about the idea that multiple mappings might one day be possible/necessary.
Especially as we move towards multi-state perturbations, multiple mappings may be important here. I guess the question is - is flexibility better than not?
@IAlibay sorry should've been clearer, it's taking either a single Mapping or many, so zero, one or more. Then you don't have to (but can) pass a list of a single mapping whenever you do a RFE.
Ah so Optional[Union[Mapping, List[Mapping]]? That would be great!
I should have just read the code instead of reading my emails, sorry...
was previously a
dict[str, ComponentMapping]
where the strings were arbitrary labels. These arbitrary labels were superfluous. Instead can use the arbitrary labels on ChemicalSystems to label components. (ComponentMappings can (and should) be matched against components in ChemicalSystem using the Component eq operations.)This now accepts either a single ComponentMapping (covers most cases), or None (covers ABFE), or a list (handles future things?)
also affects Transformation object, which was essentially wrapper around Protocol + ChemicalSystem