Changes between Initial Version and Version 1 of Ticket #133


Ignore:
Timestamp:
Sep 16, 2008, 9:07:19 PM (14 years ago)
Author:
Jari Häkkinen
Comment:

Now I have a better understanding of the issue. The problem is that in several cases one or more of the replicates has no defined value. The exported data is simply an empty field. In the ReplicateError plug-in these are used in computation and therefore generates a NaN that is printed to stdout.txt. BASE1 ignores NaNs? but BASE2 does not and stores them as null values. The resolution is to print an empty field rather than NaN, BASE2 will ignore these lines and hopefully BASE1 too. So, this fix is tested with Base1PluginExecuter in BASE2 but not tested in BASE1. It is expected to work also in BASE1.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #133

    • Property Owner changed from Johan Enell to Jari Häkkinen
    • Property Status changed from new to assigned

  • Ticket #133 – Description

    initial v1  
    1 This causes Base1PluginExecurter to import these reporters with null values to bioassays whereas it seems like BASE1 just ignores these lines. Rather than changing the behaviour of Base1PluginExecuter to skip such lines ReplicateError should not create these entries in stdout.txt.
     1This causes Base1PluginExecurter to import these reporters with null values to bioassays whereas it seems like BASE1 just ignores these lines. Rather than changing the behaviour of Base1PluginExecuter to skip such lines !ReplicateError should not create these entries in stdout.txt.
    22
    33The difference between BASE version 1 and 2 in this case is that BASE version 2 allows null values for intensities.