Skip to content

bug: force fitting unstable best fit #4

@Psirving

Description

@Psirving

There is a bug encountered when force fitting an unstable best fit. Line 577 in DanceMapper.py sets bestfit to None, then line 593 tries to call bestfit.imputeInactiveParams(). I'm not sure what the intended output is for this scenario.

Bestfit solution only found 1 times -- unstable!!!

Traceback (most recent call last):
  File "/nas/longleaf/home/anaaatan/DanceMapper/DanceMapper.py", line 1286, in <module>
    forcefit = True)
  File "/nas/longleaf/home/anaaatan/DanceMapper/DanceMapper.py", line 593, in fitEM
    bestfit.imputeInactiveParams(self.reads, self.mutations)
AttributeError: 'NoneType' object has no attribute 'imputeInactiveParams'

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions