FLOWJO UPDATE .EXE
FLOWJO UPDATE FULL
FLOWJO UPDATE FREE

Ellipse gates do not scale with Transformation.Workaround: Set your transforms before you compensate.On occasion, changing Transform to Log after Compensating the Compenation group locks up the X-Axis and T button.Workaround: Select a different sample’s keyword field, then reselect the keyword to copy.“Copy value to group” Is sometimes disabled after editing keyword.Adding fcs files to template workspace does not show Calculating on initial calculations.

FLOWJO UPDATE FULL

Fixed an issue where the selected parameter in the Layout Editor graph plot where the Y axis was not displaying the full name of the parameter.

Fixed a problem where keyboard shortcuts would not work in numeric text fields.

Fixed an issue in Population Comparison where the bin setting would be lost when the platform was closed.

Fixed an issue where XML Excel table export did not contain a header row.

Improved the default scaling of Yeti data.

Fixed an issue where we were erroneously filtering out height parameters in some cases.

Found and fixed an error in combination gates applied (dragged) to sibling populations.

Fixed a rare issue where some data files would shows No $PnS Keywords/Labels.

Fixed an issue saving the Miltenyi Transform in Customize Axis Dialog.

Fixed a rare issue with Mo-Flo Astrios Files regarding the parameter filter string.

Fixed an issue where Layout overlays reverted to default properties when changes to legend were applied.

Better handling of fcs files with null entries in matrix file.

(A side effect of this is that you will see a dialog asking if you want to save a workspace even though it hasn’t changed)

Fixed an issue where very large and complex workspaces could take a very long time to close.

Improved the file saving behavior with ACS files.

For a digest of these release notes, please see this page. The bigger the number, the 'smoother' the flowjo experience, but also - higher RAM utilization.Below are the exhaustive release notes and known issues. This setting controls how many calculations the engine should remember.

FLOWJO UPDATE FREE

For faster computers / faster hard drives, feel free to increase this setting if increasing the number of engines does not help. This is how much data an Engine will read at each cycle. Please note, free RAM is the free physical RAM remaining after you open FlowJo, not how many GB are installed total. Recommended value = (your computer's free RAM in GB / size of your FCS data x2 in GB ). As you increase the number of Engines or Threads per Engine, it's good to lower this. This setting controls how many FCS files each Engine should remember.

Otherwise they will remain open for the next FJ client which starts up and reconnects to the.

FLOWJO UPDATE .EXE

exe processes related to flowjo will terminate when the last workspace is closed. If the engines crash while the GUI stays open, FlowJo will re-spawn new instances of 'EXE' engines and re-send the failed request. If the FlowJo GUI crashes, it will re-connect with the 'EXE engines after the restart. Each 'EXE' engine is it's own user-process, therefore it has it's own pool of RAM (1.7GB per engine max, we don't recommend filling them beyond 1GB for stability.) For example, to safely saturate a workstation with 8GB RAM, I would enable 8 'EXE' engines to be dispatched. We also recommend using the engine dispatcher on computers with 2 or more GB RAM. We recommend using the engine dispatcher on computers with 4 or more CPU's. The number of EXE engines can be user specified in the 'Local Engines to use' setting. If on, this will load the 'EXE' version of the engine, times the number specified in the text field, with optional handle for starting port number. The defualt setting is (number of processors + 1), but if you notice your CPU's are sub-saturated, you may wish to increase this number or launch more Engines (via the Dispatcher preference.) Most notable result of this pref will be in layout editor batching.įlowJo's Engine handles all reading/writing of FCS data, and performs all calculations/manipulations of the data while in memory. This preference requires that the program is restarted in order to be updated. This integer tells FlowJo how many threads the Graphical User Interface should open at the start of the program. Variables like compensation error and biexponential transform setting may affect contents of gates, which in turn affect statistics. This is sometimes necessary when importing workspaces from older versions, or from other people's workstations. This preference will force the workspace to refresh all of its gates and statistics. Welcome! this page will thoroughly explain all the settings on the 'performance' tab of FlowJo's preferences.

Flowjo update