What to include
For workflow questions, include the package mode, input type, browser behavior, and any concise error text that helps reproduce the issue.
Questions, bug reports, deployment feedback, and collaboration inquiries.
Questions, bug reports, deployment feedback, and collaboration inquiries can be sent to Joseph-Michael Schulz at jmschulz@med.miami.edu.
Before sending files
Please avoid sending confidential receptor structures, proprietary ligand libraries, private deployment credentials, or sensitive project data through public channels. Use small non-confidential examples when possible.
Code-specific issues
For code-specific issues, include the relevant route, template, dependency, deployment environment, and link to the repository: https://github.com/Joey305/autodock-WEBSERVER.
Confidential data
Do not send confidential structures, proprietary ligand libraries, or sensitive deployment details through public tools without appropriate controls.
Companion tools
For ecosystem questions, mention whether your workflow touches docking preparation, warhead review, E3 recruiter exploration, PROTAC design, V-LiSEMOD, or Pymacs.
FAQ
Contact FAQ
What makes a workflow question easier to answer?
Include the page or API endpoint, the input format, package mode, concise error text, and the step where behavior diverged from expectations.
Should I report scientific interpretation questions here?
This contact path is best for PrepServer workflow, code, deployment, and packaging questions. Docking interpretation should be reviewed with the relevant scientific team.
Can I ask about deployments or collaborations?
Yes. Include the intended deployment context, whether it is public or private, expected users, and any constraints around authentication, storage, cleanup, or API use.