Few things interrupt a modeling workflow like finishing a structure and then discovering that a collaborator’s software cannot open the file—or that you are not sure which format to choose. Exporting is the step that turns content in a SAMSON document into a file another tool or person can use. A small amount of planning can make that handoff much smoother.
Start with the next step, not the file extension
Before exporting, ask what the file needs to do next. Is someone going to inspect a molecular structure, use it in another application, or work with a visualization? The answer helps narrow down which format to consider. SAMSON includes default exporters for common structures and visualizations, and exporters can write formats such as PDB and XYZ. The available choices depend on the supported formats and installed extensions.
When a recipient requests a particular format, confirm that it is supported for export in SAMSON. The supported formats reference is the place to check the format list. This is more reliable than choosing an extension based only on what another application happens to accept: a format may be supported for importing, exporting, or both.
Keep reading and writing distinct
A useful way to avoid a common source of confusion is to separate the two directions of file handling:
- Exporters write content from a SAMSON document to files.
- Importers read files into SAMSON.
The two extension families are related, but they serve different jobs. If your goal is to save a document’s content for use elsewhere, look for an exporter. If your goal is to bring an existing file into SAMSON, look for an importer. The importers reference describes the matching family for reading files.
A quick handoff checklist
- Identify the recipient’s needs. Ask which format their workflow expects, rather than guessing from a familiar file extension.
- Check the format list. Confirm that the requested format is supported by SAMSON and is available for the direction you need: export or import.
- Choose the appropriate exporter. Exporters are the extensions responsible for writing document content. SAMSON provides default exporters for common structures and visualizations; additional exporters can be added through SAMSON Connect.
- Review the handoff. After creating the file, make sure it is the file you intend to share and that its format matches the recipient’s request. When possible, have the receiving workflow confirm that it opens as expected.
- Resolve missing formats at the source. If the exporter you need is not available, check the supported formats reference and consider whether an extension is available through SAMSON Connect.
When the exporter you need is missing
A missing option does not necessarily mean the document cannot be shared. First, check the supported formats list for another format that meets the recipient’s needs. If no suitable exporter is listed, SAMSON’s documentation directs users to contact the SAMSON team. Developers who want to build an exporter can start with the documentation on generating SAMSON Extensions and the Documentation center. For a broader overview of extension-based capabilities, see Extending SAMSON.
The key is to treat export as part of the handoff, not an afterthought: identify the destination, verify the supported format, and use an exporter to write the document content. For the exporter reference and related resources, learn more in the SAMSON documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.