Skip to content

qpcr (v3.1.1)

Compare
Choose a tag to compare
@NoahHenrikKleinschmidt NoahHenrikKleinschmidt released this 19 Feb 22:53
· 383 commits to main since this release

This update introduces support for a new type of Big Table, as well as a filetype independent Parser. Furthermore, Plotter default settings were slightly adjusted, which only affects the Figure's default labelling, however.

New "hybrid" Big Table support

"Hybrid" Big Tables store their replicate identifiers in a dedicated column, while storing Ct values for separate assays in side-by-side columns. Hence, they combine aspects from horizontal and vertical big tables. Support for this data arrangement was added as a feature of the BigTableReader.

Extended "regular" file support

Regular files may now also store additional data columns apart from replicate identifier and Ct values. However, in this case column names must be supplied while reading. Furthermore, users may now force reading a file as "regular" using is_regular = True (this only works for the SingleReader) to prevent the Reader from calling Parsers. This was primarily implemented to avoid the Parser-generated assay_pattern related error messages from regular files when the true reason for failure were wrong specified column names.

The ArrayParser

The ArrayParser, contrary to the already existing CsvParser and ExcelParser, does does not rely on a specific filetype but adopts an existing numpy.ndarray using its read method.

New id_label and altered id handling.

Objects are identified by qpcr through their id attribute. The id attribute is now supported by a secondary id named the id_label, which can be arbitrarily set or automatically generated by splitting the actual id using simple string operations or regex matching. To that end new methods id_label , split_id , and merge_id are introduced and are available for all qpcr classes that inherit from the auxiliary _ID. �id_label and id can be repeatedly switched using id_to_label. Also, a merged id can be generated without the object adopting it using get_merged_id. Finally, id_reset (which must be called before a new object id can be set) is now a public method.
This was done in an effort to allow more facilitated comparison of transcript isoform assays, which is a planned feature of a future release.