From Installation to First Launch: A Clear Path into SAMSON

Installing molecular-design software is only one part of getting started. The next questions tend to arrive together: Will it run on my computer? Where do I launch it? What should I do first—and where do extensions fit in? A little planning can make the first session less about searching menus and more about getting oriented.

This guide turns the SAMSON setup information into a practical sequence: check your system, install and launch the platform, then choose a sensible next step for your work.

Simulation of 1PV7 in SAMSON
A molecular simulation in SAMSON.

1. Check the computer before installing

Start with the Requirements and platforms guide. It covers supported operating systems, hardware expectations, and Linux dependencies. Checking these before installation helps you identify platform or graphics considerations early, rather than treating every launch issue as an installer problem.

If the installation or graphics setup does not behave as expected, use the Troubleshooting guide. Linux users with AMD/ATI graphics cards can also go directly to the relevant Linux AMD troubleshooting section.

2. Follow the installation path

Once you have checked your system, follow Install SAMSON. That guide covers the installer workflow, including sign-in and key entry. Keeping installation and first-use questions separate can make it easier to pinpoint where you need help: use the installation guide for setup, and the launch instructions below for opening the application afterward.

The documentation identifies 2026 R1 as the current public version. For an explanation of version numbers, see Versioning.

3. Know where to launch it

The launch route depends on your operating system:

  • Windows: Search for SAMSON from the Start menu. The documented executable location is C:/Users/%USERNAME%/OneAngstrom/SAMSON-Application/11.0.0/Binaries/SAMSON-Core.exe.
  • Mac: Open SAMSON from Launchpad or the Applications folder. The documented installation folder is $HOME/Applications/SAMSON.app/.
  • Linux: Start it from the Apps dashboard, or run ./SAMSON-Core.sh from the Binaries folder in the installation directory. The documentation also shows how to create a shell alias if you prefer to launch it by typing samson in a terminal.

These paths are useful when the application shortcut is hard to find or when you need to confirm how the platform is launched on your system. Installation paths can vary, so if the documented location does not match your computer, refer to the installation instructions for your setup.

4. Choose a first task—not every feature

A new platform can feel difficult when the first goal is simply “learn everything.” Instead, choose the next guide based on the task in front of you:

This task-first approach keeps the learning path relevant: you can learn the interface when you need orientation, or move directly to opening a structure when that is your immediate goal.

5. Think of extensions as workflow choices

SAMSON has an open architecture, and its extensions include apps, editors, controllers, models, and parsers. They can support tasks such as building models, performing calculations, running simulations, visualizing results, and adapting the platform to a particular domain or workflow.

On first launch, SAMSON downloads a set of default extensions. You can later sign in to SAMSON Connect, visit the Marketplace, and choose extensions that match your needs. There is no need to make extension management your first task unless you already know what your workflow requires. When you are ready to explore it in more depth—including the SDK path—read Extending SAMSON.

The practical sequence is simple: check compatibility, install, launch using the route for your operating system, and then follow the guide that matches your first task. For the full onboarding details, visit the SAMSON Getting Started documentation.

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

Comments are closed.