#1516 closed enhancement (fixed)

Add support for setting the "penalty" parameter in the call to ascat.aspcf()

Reported by: Nicklas Nordborg Owned by: Nicklas Nordborg
Priority: major Milestone: Reggie v4.49.1
Component: net.sf.basedb.reggie Keywords:
Cc:

Description

We noticed that there were some samples that wasn't segmented in places were there was a clear visible break-point in the LogR data. Changing the penalty to 70 worked.

The default should still be 100, but there should be an option in the GUI to start with a different penalty.

Change History (1)

comment:1 by Nicklas Nordborg, 14 months ago

Resolution: fixed
Status: newclosed

In 7328:

Fixes #1516: Add support for setting the "penalty" parameter in the call to ascat.aspcf()

There is now a field in the "Start ASCAT" wizard for setting the penalty parameter. The parameter is displayed in the confirmation wizard and case summary.

Note: See TracTickets for help on using tickets.