A molecular model can be ready for sharing in SAMSON and still be difficult for someone else to use if it is saved in the wrong file format. A collaborator may need a structure file for another tool, a visualization file for a presentation, or a format that fits a downstream workflow. The practical challenge is not simply saving a file—it is choosing an exporter that matches what the recipient needs.
Start with the destination
Before exporting, ask where the file is going and what it needs to contain. Is it intended to be opened in another molecular modeling application, used in a workflow that expects a particular structure format, or shared as a visualization? The answer helps narrow down the format to look for. SAMSON exporters write document content to files; examples include PDB and XYZ, alongside other supported formats.
If you are unsure which formats SAMSON can read or write, consult the supported formats list. Checking this first can prevent a common handoff problem: choosing a familiar file extension without confirming that it serves the recipient’s purpose.
Think of the exporter as the format-specific step
An exporter is the extension responsible for writing document content in a particular file format. SAMSON includes default exporters for common structures and visualizations. Additional exporters can be added from SAMSON Connect.
This distinction is useful when a format seems to be missing. Rather than assuming that every possible format is included by default, check the supported-format reference and consider whether an additional exporter is available. If you cannot find the exporter you need, the documentation suggests contacting the SAMSON team.
A simple handoff checklist
- Confirm the recipient’s requirement. Ask which format their application or workflow expects. A format that is convenient for one purpose may not be suitable for another.
- Check support before exporting. Use the supported-formats page to see which formats SAMSON can import and export.
- Find the matching exporter. SAMSON has default exporters, and more can be added through SAMSON Connect.
- Review the resulting file in context. When possible, open the exported file in the intended destination application or ask the recipient to confirm it works for their task. This is a practical handoff check, not a substitute for knowing what the destination expects.
- Keep the original document available. If requirements change, returning to the SAMSON document makes it easier to prepare a different export rather than treating one exported file as the only copy of your work.
When the right exporter does not exist
If you need a format that is not covered by an available exporter, there are two useful paths. For an existing capability, check SAMSON Connect for additional extensions. If you want to build the capability yourself, the documentation points to the guide for generating SAMSON Extensions and the Documentation center. The broader Extending SAMSON reference explains extension-based capabilities.
It also helps to distinguish exporting from importing. Exporters write document content to files; importers are the matching extension family for reading files into SAMSON. If your issue is opening a file rather than saving one, the Importers reference is the relevant starting point.
For a concise overview of exporter extensions and related references, see the SAMSON Exporters documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.