Hi Everyone,
PerkinElmer Informatics is pleased to announce the release of High Content ProfilerTM 1.3, which enables browsing, searching, downloading, and aggregation of Columbus contents directly within High Content Profiler and Spotfire.
Highlights of High Content ProfilerTM 1.3 release include the following:
New Columbus data source to search, filter, browse, and preview data and images stored in the Columbus database directly within Spotfire and High Content Profiler.
o Search and filter by any data and metadata types
o Automatic relationship management between cell and well level data
o Automatic aggregation of multiple wells and plates for both cell and well level data files into a single table
o Automatic aggregation of data and plate layout information (assay definition) into a single table
Seungtaek Lee | Informatics – Product Manager
PerkinElmer | For the Better
HUMAN HEALTH | ENVIRONMENTAL HEALTH
Below are some additional information from our release notes:
Known Issues, Limitations, and Workarounds
Limitations and Known Issues:
- Cannot preview the result image of a Columbus rule in insert/edit images column dialog, even if user has logged in.
- Group rule name may be duplicated on preference page.
- Message box of applying image settings may pop up even if we did not change anything.
- Out of memory exception may occur while processing large images (around 300MB).
- The High Content Profile HTML panels may have incorrect width and show a horizontal scroll bar when the installed Internet Explorer version is 8
- If the user changes from ‘custom’ normalization data function to a normalization data function provided by High Content Profiler 1.3 in an executed workflow, using ‘Analysis settings’, the new execution will fail. This also happens if the user tries to change from a normalization data function provided by the High Content Profiler 1.3, to a ‘custom’ normalization data function using the ‘Analysis settings’. To avoid this issue the user should re-execute the workflow (using the wizard) when changing between user and workflow defined normalization data functions.
In Spotfire 7.0 if the user changes the Spotfire Visual Theme the HCP html panels will remain white.
- Normalization will not work correctly on the plates with no controls if the user provides a dataset containing controls in some plates but not in others.
- The HCP workflow may fail if a new execution is attempted before the previous execution completes.
- The dose response page will only display the first 5000 compounds if more than 5000 compounds are loaded.
- When using multiple un-pooled controls the positivity score for the different controls is not available in the dose response dropdown menu. These values can still be displayed by selecting them manually on the respective axes or executing the workflow separately for each of the controls.
- In Columbus, you cannot create assay layouts with identical layer names, however, this is not prevented during the import process and an error may result.
List of Fixed Defects
The following issues were fixed with this release:
- When no controls were provided the color selector in the plate layout overview page did not work correctly
- The presence of special characters in the values of certain columns could cause problems in various visualizations when these columns were selected and prevent the correct display of the Hits per compound table.
- The presence of some special characters in the compound column name would cause an incorrect display of the prediction details visualization
- The plate layout editor html panel is now cleared after the user selects the HCP tool to perform a new workflow execution
- Workflow execution was extremely slow when the compound column had many unique values
- In the dose response all compounds were selected by default, this could cause problems when the number of compounds high.
- When many compounds are present the visualizations in the dose response page never loaded.
- The presence of special characters in the feature names could produce an error in the dose response visualization
- Removed the none entry for compound selection in the dose response page, as it makes no sense to display no compound
- In certain cases numeric values were interpreted as strings in the Plate layout editor, which could cause problems if the layout column was intended for use as numeric.
- Hits per compound table was missing some columns if concentration was not provided