Skip to content

Projects

A project is the whole analysis: every node, every gate, the links between them, where the nodes sit on the canvas, and the set of scales the parameters use. It is saved as a single .ppj file.

A project does not contain the data. Open the plate first, then load the project on top of it - or load the project first, and it will hold its scales until a dataset arrives.

Saving

Click Save project on the toolbar. The dialog opens in the INFO folder of the currently loaded data, which is where projects belong: a .ppj sitting next to the data it describes travels with it, and anyone who opens that folder finds the analysis.

The project name appears in the toolbar next to the data folder name.

Loading

Click Load project and pick a .ppj. If the current project has unsaved changes and Annoying Mode is on, you are offered the chance to save first - see below.

You can also:

  • Use the History window, which lists both recent data folders and recent projects.
  • Pass a project as the second command-line argument, after a data folder:

    PlatAnJr.exe "D:\Experiments\Plate 17" "D:\Experiments\Plate 17\INFO\screen.ppj"
    

Gates are stored by identity and re-linked after loading, so a project with a complicated graph comes back wired exactly as it was saved.

Starting over

Erase project clears the canvas. The current state is written to the backup before anything is deleted, and with Annoying Mode on, unsaved changes are offered for saving first.

The safety net

Load last saved protocol (the undo button) restores the automatic backup PlatAnJr keeps of the project. Every time you erase a project or load a different one, the current state is backed up first, so this is the way back from "I did not mean to do that".

It restores one step, not a history. It is a safety net, not an undo stack: there is no per-action undo in the project panel, so save meaningful milestones as named .ppj files.

The unsaved-changes prompt

PlatAnJr compares the project as it now stands against the state at the last save. Only real changes count - scrolling, panning, the locator and selecting nodes move nothing that is saved. A project opened from the command line counts as saved.

Whether PlatAnJr then asks is up to Annoying Mode on the MoreOptions page - its tooltip reads "Requests confirmation when the protocol is changed." With it on, Erase project, Load Project and closing PlatAnJr ask "Protocol is not saved. Save?" whenever there are changes. It is off every time PlatAnJr starts and is not kept between sessions: turn it on for the session if you want to be asked, and otherwise save as you go. Load last saved protocol stays the way back from an erase or a load.

Projects across datasets

A project refers to parameters by name. That makes a project a reusable template: open a different plate acquired with the same panel, load the project, and the same gating strategy applies to the new data.

Two things to watch:

  • Parameter names must match. If the new dataset calls a channel something else, the nodes plotting it will not find it.
  • Derived parameters are not recreated. Nodes that plot a ratio or a phasor coordinate need that parameter to exist first - create them before loading the project. See Derived parameters.

Gate positions carry over unchanged, which is the point of a template - but check them against the new data before trusting the numbers. Different staining, different day, different instrument settings all move populations.

Versions and compatibility

Projects carry a version number, and so does nearly every object inside them. Newer builds read older projects; the reverse is not guaranteed. Keep a copy of anything important before opening it in a much newer build for the first time.

Legacy .pap files from the earlier PlatAn are read-only: PlatAnJr can open them, but saves in the current .ppj format.

Gate files

For reusing part of an analysis rather than all of it, the node menu can save a node's gates to a .gat file and load them back - into the same node, a different node, or a different dataset. See Gate types.