v1.b325 (Version 1, Build 325) - Released July 4, 2017

Riffyn has just been upgraded in three big ways!


1) Riffyn no longer requires you to assign resources before you write data to runs. Resource assignment is now something you do only when you choose to do so -- e.g., because assigning a resource will automatically display the values of its fixed properties on your experiment. Data entered on non-fixed properties will survive subsequent resource assignment or removal unchanged, but data written to fixed properties will no longer be displayed if a subsequently assigned resource carries a previously specified value of the same fixed property. If you find yourself writing data to fixed properties prior to resource assignment, consider using Plan mode instead. You can read more detail about fixed properties here.

 

2) When you view resources in the inventory you can now request to “Load Resource Use Details”:

Pressing this button returns a list of the experiments where the resource has been used:

Double clicking on any row of this table will open the corresponding experiment in a new tab.

 

3) We have streamlined the UX for deleting one or more entities from the libraries. E.g., after you have used shift-click to select multiple processes you can then select “Move to Trash” from any of the selected menus on the right. The deleted entities can be rescued from the Trash up to 7 days after they have been moved there.

 

The new release contains these additional features and bug fixes.

 

New Features 

Design & Measure:

Reminder: if you find yourself writing fixed property values via Parsely to input or pass-through resources, consider saving yourself the trouble. It is usually the case that those fixed property values have already been written to those resources and do not need to be overwritten.

  • All image and video files that have been uploaded to Riffyn can now be expanded to full screen.
  • There are no longer any restrictions on the kinds of files you can upload as attachments to procedure tasks, design notes or observations.
  • The “Make Samples Of…” feature has been enhanced with a complimentary and functionally equivalent option to “Make New…” For example, if your step transforms your cell culture in a flask into a set of new cell cultures in sample vials, you might ask Riffyn to issue new RifIDs for each sample by selecting “Make Samples Of…” On the other hand, if your step transforms a cell culture in a flask into a new set of cell cultures in a new set of flasks, you might ask Riffyn to issue new RifIDs for each new flask by selecting “Make New…”

Analyze:

  • Input values are no longer cleaned automatically. Exported column headers that used to read “Step | input | Resource Type | Property | value | mean” by default will now read “Step | input | Resource Type | Property | value” by default.
  • Data Cleaning interfaces have been updated to accommodate input properties as well as output properties.

 

Issues Fixed

General:

  • Once again users can view their Profiles from the User menu in the top right corner of the application

 Design & Measure:

  • Some issues encountered when reordering tasks using the cross-step task viewer have been fixed.
  • In the Attachments panel the Current Step column now shows data for all 3 kinds of attachments (Procedure, Design Notes and Observations).
  • Users with Viewer access to Processes could not upload, download or delete data files on the Experiments that were shared with them as Operator. This is now fixed.
  • All images uploaded to procedure tasks should now be displayed correctly.
  • Sharing an Experiment with a user as Operator, Designer or Admin will now grant that user Operator privileges on the corresponding Process if he did not previously have access to the Process.

Design:

  • You can no longer enter the edit state for tasks when viewing previous versions of a process. (Those edits were being saved to the working version of the process.)

 Measure:

  • Viewers are no longer presented the interface to create new runs.
  • Viewers are once again able to view run connections.
  • Parsely Configuration Preview now shows a black alert instead of a red warning if a user chooses not to write data to any properties on the step.
  • Clean Data Tab no longer shows sort carets since the rows are not sortable.
  • Units were not displayed for some properties when viewing a resource in the top panel. This has been fixed.
  • Parsely will now show an error if a run identifier has not been specified in a parse configuration.
  • All worksheets in a workbook are now accessible when defining data blocks in Parsely.

 Analyze:

  • Experiments with a split-merge run graph topology would occasionally export rows where the output resource on an upstream step was not equal to the input resource on the corresponding downstream step. This bug has been fixed in a way that has introduced gaps in the exported table where previously there were no gaps. Both representations of the data are accurate, and each has distinct advantages for data analysis. We intend soon to give users control over which form is used for data export.
  • Single-valued data are now automatically exported on all rows associated with a run, so what you see in the multi-value editor (top panel) is now always the same as what you get upon export. As part of this implementation we decided to stop exporting the “File id” columns for the time being.
  • Viewers are once again able to request calculation and export of Riffyn data files.

 Library:

  • Designers can now remove members from a team.
  • For Mac users the key mapping for selecting multiple entities in the libraries has been updated from the “control” key to the “command” key.

 

Known Issues

We intend to resolve the following issues with our next release in ~4 weeks:

  • If a sufficiently large amount of data has been written to an individual run, Riffyn will ask users to Clean Data before export. The current issue is the confusion that results when sometimes -- but not all the time -- a trivial Data Cleaning Procedure (which doesn’t actually clean the data at all) proves sufficient to export the data.
  • If a user switches the order of two tasks on the same step using the cross-step viewer he is subsequently unable to reverse the switch when viewing the same tasks on the step itself.
  • Users are unable to create new character properties while adjusting the process design in Measure Mode
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request