Split pathsimulator.py#754
Conversation
|
Passes tests. Ready for review/merge. |
jhprinz
left a comment
There was a problem hiding this comment.
Very nice. Make it much cleaner
|
Thanks -- I have some rough plans for doing the same with |
|
I would have liked an |
|
What were you importing from In order to make sure everything only shows up in only one place in the (official, public) API, I think that only the least-nested level should be used. For most of OPS, that means the root |
You are correct, thanks for the tip. This came up in one of my old E-CAM modules (the transition state ensemble). It is now fixed, and imports from the |
As mentioned in #753, we should reorganize our file structure. I'm planning to do some work on parallelizing some path simulators soon, so I'm starting by reorganizing the
pathsimulator.pyfile. Here's how I'm splitting it:path_simulator.py:PathSimulator,MCStep(will move MCStep elsewhere later)shoot_from_snapshot.py:ShootFromSnapshotsSimulation;CommittorSimulationpath_sampling.py:PathSamplingbootstrap_init_conds.py: all bootstrap stuffdirect_md.py:DirectSimulationNote that the approach I've used to split involves some git acrobatics in order to preserve history on lines within the split files. See https://beyermatthias.de/blog/2014/09/24/splitting-files-while-preserving-history-in-git/.