A problem in a molecular modeling session can interrupt more than a single task: it can leave you wondering whether you need a quick answer, a practical fix, or detailed information about a feature. When those needs get mixed together, it is easy to spend time browsing documentation that does not match the problem in front of you.
A useful first step is to classify the question. Is it a recurring question, a symptom you need to resolve, or a request for details about a particular feature? SAMSON’s help resources are organized around those different needs, so choosing a category first gives you a clearer starting point.
Three kinds of questions, three starting points
- “Is there a quick answer to this common question?” Start with the FAQ. It covers recurring questions about accounts, installation, updates, and extensions. Use it when you suspect your question has a short, direct answer.
- “Something is not working as expected. What should I try?” Go to Troubleshooting. This is the better fit when you can describe the issue by its symptoms and need a practical path toward a fix.
- “I know which feature I’m using, and I need its details.” Open References. It is a jump point to reference material for specific SAMSON feature areas.
A quick triage routine
- State the question in one sentence. For example: “I have a question about an extension,” “I’m seeing a problem,” or “I need details about a feature.” You do not need to solve the problem yet; the goal is simply to identify what kind of help you need.
- Choose the closest category. A recurring account, installation, update, or extension question points to the FAQ. A problem described by what you observe points to Troubleshooting. A question about how a specific feature is documented points to References.
- Start with one resource. Avoid opening every section at once. Begin with the page that matches your question, then change paths if you discover that your original diagnosis was off.
- Skip what does not help. If you only need a quick answer or fix, you can leave the broader reference material for later. If the issue is clearly symptom-based, you can go directly to Troubleshooting rather than starting with the FAQ. If you need a feature reference, you can skip troubleshooting.
This small distinction matters because “I need help” is not yet a useful search direction. “I need a recurring answer,” “I need to diagnose a problem,” and “I need the reference for this feature” are much easier to act on. It also helps avoid treating every issue as a troubleshooting case or searching reference pages when a concise FAQ answer may be enough.
When your question changes
It is normal for the right path to become clearer as you investigate. You might begin with a general question and realize that the real issue is a specific symptom. Or you may start troubleshooting and discover that what you need is a feature’s canonical reference. Switching resources is not wasted effort; it is part of narrowing down the question.
For example, begin with the FAQ if you have a general question about installation or extensions. If your situation is instead defined by a particular problem, move to Troubleshooting. If you already know the feature area and want its detailed documentation, go directly to References. The aim is not to read everything—it is to find the kind of answer that fits your immediate need.
If you are unsure where to begin, use the FAQ as the first stop. If the problem is plainly symptom-based, go straight to Troubleshooting. For the complete overview of these routes, see the SAMSON Reference and help page.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.