A molecular modeling session can be interrupted by very different kinds of problems: a question about an account or installation, an unexpected platform behavior, or uncertainty about how a particular feature works. When these are all treated as the same kind of issue, it is easy to spend time searching the wrong place.
A more efficient approach is to identify what kind of help you need before you start browsing. SAMSON’s help resources offer three routes: recurring questions, symptom-based troubleshooting, and detailed feature references. Choosing among them is a small step that can make the next step much clearer.
First, name the problem
Ask yourself which description best matches what you are trying to solve:
- “I have a common question.” You may be looking for information about accounts, installation, updates, or extensions. Begin with the FAQ, which is intended for recurring questions.
- “Something is not working as expected.” If you can describe the issue by its symptoms and want a practical path toward a fix, go to Troubleshooting.
- “I know which feature I need to understand.” If your question is about a specific SAMSON feature area, use References to find the relevant detailed reference family.
This distinction is useful because a “how does this feature work?” question and a “why is this not working?” problem call for different kinds of information. A reference page helps explain a feature; troubleshooting is organized around symptoms; an FAQ is a quick starting point for common questions.
A practical decision path
- Start with the FAQ when the question is recurring. This is a sensible first stop if you are unsure whether your issue is common or related to an account, installation, update, or extension.
- Switch to troubleshooting when the symptoms are clear. If you already know what is going wrong, do not feel you have to read through every general question first. Go directly to the troubleshooting path.
- Use references when you need feature detail. If the problem is really about understanding a feature rather than fixing a symptom, the reference hub is the more direct route.
In short: quick answer → FAQ; problem to fix → Troubleshooting; feature details → References. You do not need to follow all three in order. The recommended reading order is a useful default, not a requirement to visit every page before getting help.
Make your search more focused
Before opening a help page, write down the question in one sentence. For example: “I need a recurring answer about an extension,” “I am diagnosing a platform problem,” or “I need the detailed reference for a feature area.” This simple habit helps you choose the right resource and keeps you from confusing a request for feature information with a request to resolve an issue.
It can also help to pause when a search result seems close but not quite right. Ask whether you need an explanation, a fix path, or a quick answer. If the category has changed, change routes too: a question that begins as a feature question may reveal a runtime problem, while an apparent problem may turn out to be a request for reference details.
When your question is part of a larger task
Not every question belongs in the help-and-reference path. If you are still getting oriented, continue to Start here for installation, first-use orientation, and onboarding follow-up. For SAMSON Connect, permissions, groups, or shared documents and jobs, visit Share and collaborate. If you are looking for scripting, extensions, or developer-facing workflows, see Automate and extend.
The goal is not to read more documentation than necessary. It is to land on the kind of help that matches the problem in front of you, so you can get back to your modeling work with less searching.
For the complete overview, visit the SAMSON Reference and help page.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.