When a Molecular File Won’t Open: A Practical Importer Checklist

You have a molecular structure, density map, mesh, or other scientific file ready to use—but SAMSON does not load it as expected. Before trying random workarounds, it helps to identify the part of the process that matters: an importer is the extension that reads a file and brings its contents into a SAMSON document.

This distinction can save time. A file may be valid in its own format while still requiring an importer that SAMSON does not currently have available. Here is a straightforward way to investigate the problem and decide what to do next.

1. Check the format, not just the filename

Start by identifying the actual file format and what the file contains. Is it a molecular structure, an electron-density map, a mesh, or another kind of object? Importers handle particular formats and object types, so knowing both the format and the intended content helps you find the right information.

A filename extension can be a useful clue, but it is not a complete description of the file. If you are unsure, check how the file was created or consult the source that provided it. Avoid changing the extension simply to make it resemble a format you know; that does not convert the file’s contents.

2. Look for the format in SAMSON’s supported-format list

Next, check the formats supported by SAMSON. This is the relevant lookup when you need to know whether SAMSON can import a particular format. It also lists export support, so pay attention to whether you are checking the direction you need: importing means reading a file into SAMSON, while exporting means writing a file out.

If your goal is simply to open a local file or fetch a structure, the task-focused Loading molecules page is a better next stop. The importer reference explains the extension family; the loading guide covers the user workflow.

3. Consider whether an importer extension is available

SAMSON includes default importers, and additional importers can be added from SAMSON Connect. In other words, the format you need may depend on an importer extension being available, rather than being handled by a default importer.

This is a useful distinction when troubleshooting: first establish whether the format is supported, then check whether the relevant importer is available in your setup. If it is not listed as supported, repeatedly retrying the same file-opening step is unlikely to answer the underlying question. You may need another supported representation of the data or a suitable importer.

4. Keep importing and exporting separate

Importers and exporters are related, but they do different jobs. An importer reads a file into SAMSON; an exporter writes data from SAMSON to a file. If you are trying to bring data into a document, an exporter is not the extension you are looking for. If you need to save your work in a particular format, consult the Exporters reference instead.

5. If the importer is missing, choose the next step

If the format you need is not supported, the documentation suggests two useful routes. If you are a user looking for an importer, you can contact the SAMSON team. If you want to build an importer yourself, start with the documentation on generating SAMSON Extensions and the Documentation center. The broader Extending SAMSON page is also relevant when you want to understand extension-based capabilities.

A useful troubleshooting note to keep with a file is its format, the type of data it contains, and whether you confirmed that an importer for it is supported and available. That small record makes it easier to explain the issue to a collaborator or ask for help without having to retrace your steps.

For the full importer reference, learn more about SAMSON importers.

Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.

Comments are closed.