You have finished preparing a molecular model and are ready to share it, analyze it elsewhere, or archive it. Then comes a deceptively practical question: which file should you create? A file that works for one recipient or tool may not be the right choice for another, and a successful export is only useful if the resulting file suits its purpose.
In SAMSON, exporters write content from a document to files. Examples include PDB and XYZ, along with other supported formats. SAMSON provides default exporters for common structures and visualizations, and additional exporters can be added through SAMSON Connect. The key is to treat format selection as part of the handoff—not as an afterthought.
Start with the person or tool receiving the file
Before exporting, identify what the file needs to do. Is it intended for another person to open, for a downstream application to process, or simply to preserve a particular representation? Ask the recipient which format they can use, or check the requirements of the next tool in your workflow. If there is no specific requirement, consult SAMSON’s supported formats reference to see which formats SAMSON can import and export.
This small check can prevent a common handoff problem: choosing a familiar extension without confirming that it fits the receiving workflow. The format name is a useful starting point, but the recipient’s needs should guide the decision.
Think of export and import as two sides of a handoff
An exporter writes document content to a file. An importer is the matching extension family for reading files. If you are planning a round trip—exporting a file and later opening it again—consider both sides. The fact that a format appears in an export workflow does not, by itself, tell you what another application will do with it. Likewise, the available importers and exporters are not interchangeable concepts.
A simple handoff checklist helps keep the process clear:
- Purpose: Decide what the recipient or next application needs the file for.
- Format: Check the supported-formats reference, and confirm any requirements with the recipient.
- Exporter: Use the available exporter that corresponds to the format you need. If you cannot find one, check whether an additional exporter is available through SAMSON Connect.
- Verification: When the handoff matters, ask the recipient to confirm that the file opens and is suitable for their intended use.
What if the exporter you need is missing?
The available formats depend on the exporters present in your SAMSON setup. SAMSON includes exporters for common structures and visualizations, and more can be added from SAMSON Connect. If the format you need is not available, the documentation suggests contacting the SAMSON team rather than assuming that a similarly named format will meet the requirement. For a missing exporter, you can write to contact@samson-connect.net.
If you are developing an exporter yourself, the user reference points to the documentation for generating SAMSON Extensions. For broader information about adding extension-based capabilities, see Extending SAMSON.
The practical takeaway is simple: choose an export format based on the next step in your workflow, verify that SAMSON supports it, and confirm that the file meets the recipient’s needs. For the format list and exporter overview, visit the SAMSON Exporters reference.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.