v1.b400 (Version 1, Build 400) - Released September 11, 2017
Riffyn has just been upgraded!
You can now aggregate runs in Execute by the unique values in any column. You can turn on this feature by clicking on any header and selecting "Aggregate by..." When runs have been aggregated the bottom panel will update in a number of ways:
1) The header of the column you are aggregating by will appear dark gray.
2) The number of objects rendered in the bottom panel will be reduced from the number of runs on the step to the number of unique values in the "Aggregate by..." column. In the example above, 384 runs representing the distinct cell culture resources in each of 384 wells collapse to just 4 objects, one for each 96-well plate.
3) If more than one distinct value of a property has been written to the individual runs within each aggregation, the corresponding cell will display an aggregation of the individual values. By default Riffyn displays a sorted list of the unique values, but the aggregation method for each property can be customized. For example, numeric properties can be aggregated as the Mean, Range, Min, Max or Median of the individual values. Process Admins and Designers can save aggregation settings for any step to the process itself, so that future experiments will display data according to the stored aggregation methods every time that step is selected.
4) Empty check boxes at left are replaced with aggregation icons that reveal a check box on mouse-over. Selected run aggregations can be flowed to other steps.
For the time being users must turn off the run aggregations before they can manually edit any data on the runs. If you select one or more run groups and then select "Show individual runs" from the context menu on any header, the bottom panel will automatically snap to the first of the selected runs.
The new release contains these additional enhancements and bug fixes.
Design & Measure:
- ENTER key now adds line breaks when editing Process or Experiment description.
- You can now download a file from a Procedure Task in an edit state.
- Text wrap has been re-enabled when editing Procedure Tasks.
- Various UI tweaks have been made to the Attachments panel.
- Default units for "time (duration)" have been set to seconds.
- Designers can once again rename Processes.
- Pressing ENTER in the "Target" field for a Property of the "Character" data type is interpreted as a request to add a new Property.
- Focus now stays in the Units drop-down menu when using a keyboard to select Units.
- Exception Loops within the full-process task order can now be removed from the last task in the loop.
- Resource Assignment Manager (top panel) now opens more quickly. This performance improvement was achieved primarily by switching the default mode for the Resource Finder (top left) from Filter to Search. Also, the Filter mode now loads data for only the top 200 results (it was previously 1600).
- The Resource Viewer (top middle) is now refreshed to display any values picked up by the Resource upon assignment to a run.
- If user has changed the displayed Resource Type in the Resource Assignment Manager, "Create New" will now create a resource with the displayed Resource Type (instead of the Resource Type designed on the step).
- When creating a new Experiment its first step is now selected automatically.
- Experiments in the Experiments Library modal can now be sorted by version in the expected way.
- Individual Configurations can be more easily selected within the Collections panel of the File Setup modal.
- In some cases where the Current Step was selected in the Configurations panel of the File Setup modal, configurations not on the current step were displayed. This has been fixed.
- In some cases where the Current Step was selected in the Configurations panel of the File Setup modal, configurations on the current step were not displayed. This has been fixed.
- If user uploads data to multiple steps while in Flow Mode, both screens are now refreshed automatically after all data has been uploaded from the file.
- Some legacy data files were not appearing in the FILTER drop-down. This has been fixed.
- Viewers are no longer able to open the file upload modal.
- Correct units are now displayed for numeric Properties associated with Components.
- Calculated Properties are once again excluded from the Property Rules interface.
- Run paths have been regenerated for all experiments to ensure consistency with designed export behavior.
- There were edge cases where combinations of single- and multi-valued data were not exported in the same form as they were being rendered in the multi-value data editor. This has been fixed.
- If export is requested at the process level, Riffyn will utilize its previously calculated files for experiments that have not been modified since the last export request.
- If export is requested from any one experiment, its data will be re-calculated using the latest version of our export service.
- If you think your data files could benefit from these updates to our export service, you can align your exported data files with this latest version using the exportExperiment API with refresh = True. If you want to achieve the same outcome without the API, you must first edit your experiment in some way (e.g., add-then-delete a run on Step 1) before triggering calculation or export in the normal ways.
- Requests to export all process data will be processed using only the experiments the user has access to.
- Performance has been improved for Data Cleaning procedures utilizing either sliding window or exact match methods.
- If user requests export for a file that Riffyn estimates to be larger than 2 GB, it will prompt user to Clean Data before export.
- Data Cleaning back-end has been re-factored to facilitate processing individual runs with >500 MB of multi-valued data.
- Property columns in data exported from an experiment are now in the same order as they appear in our UI.
- Property columns in data exported from a process are now grouped together across all experiments and process versions according to their shared Permanent Step ID (S#).
- The file_id column has been temporarily removed from exported data.
- The event_id column for each step is now exported ahead of its first input column (as opposed to its first output column).
- Experiments without any runs are no longer included in export.
- Public entities cannot be shared except by those who have been shared directly.
- Public Resource Types and properties are viewable.
- The updateRun endpoint has been created for editing run name and type.
- A collection of shareX and unshareX endpoints have been created to control access to Processes, Experiments and more.
- The listResources endpoint has been updated to allow filtering requested resources by Resource Type