Open ianscottknight opened 1 year ago
I concur. good call. As much as makes sense, we should expose useful tools for ad hoc use.
On Thu, Dec 1, 2022 at 10:05 PM Ian Scott Knight @.***> wrote:
Per #6 https://github.com/docking-org/pydock3/issues/6, plots are made in DockOpt only for the retrodock job with the best enrichment. This was intended to reduce the runtime of DockOpt for large number of tested docking configurations, as seeing plot generally only matters for the best job(s). After talking with Seth Vigneron @.***), I realized that it would be desirable for the user to be able to generate these visualizations of finished retrodock jobs on the fly in the command line (see #22 https://github.com/docking-org/pydock3/issues/22).
E.g., "pydock3 retrodock - plot" or something like that.
— Reply to this email directly, view it on GitHub https://github.com/docking-org/pydock3/issues/25, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIR2HY5ECLS7F2M7SS5XRTWLGGSTANCNFSM6AAAAAASRR7ZEI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Per #6, plots are made in DockOpt only for the retrodock job with the best enrichment. This was intended to reduce the runtime of DockOpt for large number of tested docking configurations, as seeing plots generally only matters for the best job(s). After talking with Seth Vigneron (seth.vigneron@ucsf.edu), I realized that it would be desirable for the user to be able to generate these visualizations of finished retrodock jobs on the fly in the command line (see #22).
E.g., "pydock3 retrodock - plot" or something like that.