Skip to content

Getting started

ProcessDB is a desktop application that connects to a central ProcessDB database. The models, experiments, and data you work with live in that database, not on your computer, so you can move between machines and colleagues can see the work you commit.

Installing

Integrative Bioinformatics sends you a download link for the installer. Download it and run it; the installer places ProcessDB in your applications and creates the shortcut you will use to launch it. Download links expire, so if yours has lapsed, ask for a new one rather than reusing an old installer — the newer build may expect a newer database.

You do not need to install a database, a solver, or any scientific libraries. Everything ProcessDB needs to simulate is included.

Signing in

Launch ProcessDB. After the splash screen you are asked for a username and password. The server address is filled in for you and cannot be edited — there is one ProcessDB service and your installation already points at it.

Press Login. ProcessDB loads the catalogue of models, molecules, places, processes, and experiments you have access to. This takes a few seconds; the detailed contents of individual models are fetched later, when you open them.

If you need to work as a different user — or your connection has gone stale — choose File → Reconnect…. Logging in from that dialog reloads all data as the user you name, and discards anything you have not committed. Pressing Cancel leaves you connected as you were.

What you can see

Access is controlled per model. The Filter by control at the bottom of the Models browser lets you narrow the list to:

  • All Models — everything you are allowed to see
  • Recent Models — models you have opened lately; this is the starting filter
  • My Models — models you own
  • Shared Models — models others have shared with you
  • Public Models — models published to every ProcessDB user

If a colleague's model is not in your list, switch the filter to All Models first; if it is still missing, they have not shared it with you yet.

Recovering unsaved work

ProcessDB keeps a local journal of anything you have changed but not committed. If the application or your computer stops unexpectedly, the next launch notices the journal and offers to restore that work before it loads anything from the database. Accept the offer and you are back where you were, with the same changes still uncommitted and ready to save.

Declining is safe: the journal is archived rather than deleted, so support can recover it later if you change your mind. See Saving your work for the whole picture.

Next