Service Inquiry Form
Tell me about your project. I will reply within 24–48 business hours with scope, availability, and next steps.
What to Expect After You Submit
Inquiries are reviewed personally and you will receive a reply within 24 to 48 business hours. The reply will include an assessment of the scope, current availability, and a proposed approach. No automated replies or generic acknowledgements are sent: every message is read and answered individually.
If your project falls outside the areas listed in the form, describe it in the Project Description field anyway. Many inquiries do not fit neatly into predefined categories, and custom scopes are welcomed. The most useful details to include are the biological question you are working on, the data type and approximate scale (number of samples, cells, or sequencing depth), the tools or environments you are currently using, and the specific problem or decision point where you need support.
For tutorial feedback, corrections, or content suggestions, use the same form and select "Other / Custom Request". If you have identified an error in a tutorial, include the page title and the specific section so it can be found and corrected quickly.
Common Reasons People Get in Touch
The contact form is used for a range of purposes. The most common ones are listed below to help you decide whether it is the right channel for your question.
- 1. Pipeline troubleshooting: You are running a scRNA-seq, WES, or metagenomic pipeline and have hit an error you cannot resolve. You want expert eyes on your specific error message, log file, or parameter choices.
- 2. Analysis strategy advice: You have a dataset and a biological question but are unsure which method or tool is most appropriate. You need a structured recommendation based on your data characteristics, not a generic answer.
- 3. HPC environment setup: Your institution's HPC cluster is running a particular scheduler and module system, and you need help configuring Conda, Singularity, or a Nextflow/Snakemake profile for that environment.
- 4. Manuscript methods review: You want a computational biology expert to review the methods and results sections of a manuscript before submission to ensure the analysis is described accurately and completely.
- 5. Tutorial feedback: You found an error in a tutorial, a command that no longer works with the current version of a tool, or a concept that is explained in a confusing way. These reports are especially appreciated and acted on quickly.
- 6. Content suggestions: You have a topic you wish was covered on the site, or you are working on a method that is not well documented anywhere and think it would benefit others if it were written up as a tutorial.
What This Service Does Not Cover
To manage availability and provide focused, high-quality help, certain requests fall outside the scope of services offered here. Understanding this upfront avoids wasted time on both sides. Please read carefully before submitting your inquiry to ensure it aligns with the scope of this platform. This helps maintain a high standard of support for all accepted projects.
This service does not provide interpretation of clinical findings or advice about patient care. It does not write code for requests that are entirely novel projects with no tutorial or guide attached. It does not take on requests with immediate deadlines of less than 48 hours unless discussed in advance. It does not offer support for proprietary tools that cannot be documented or discussed in an educational context.
If your request does not fit the form categories and you are unsure whether it is in scope, submit a brief description anyway. The worst outcome is a polite note explaining why it falls outside current availability, along with a pointer to a resource that might help. Your inquiry is always welcome, and every effort will be made to guide you in the right direction.