MantisBT

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001556MEGASequence Data Explorerpublic2019-11-11 11:252019-11-13 10:20
Reporterguest 
Assigned Togstecher 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusresolvedResolutionno change required 
PlatformMacOSOS X 
Product VersionMEGA 11 (Graphical Interface version) 
Target VersionFixed in Version 
Summary0001556: nice software
DescriptionN/A
Steps To ReproduceN/A
Additional InformationN/A
TagsNo tags attached.
Attach Tags (Separate by ",")
First NameMichael
Last NameLattorff
Emailmlattorff@icipe.org
Confirm Emailmlattorff@icipe.org
Attached Files

- Relationships

-  Notes
(0001351)
user19
1969-12-31 17:33

I resubmitted this for Simon. He had submitted 2 bugs in a single report.
(0001352)
user19
1969-12-31 17:33

When you first run an analysis you can see that the Runtime Progress Dialog doesn\'t draw fully. It fails to draw any of the text until there is an update a little while later. It could have something to do with a fix that Tamura added which had something to do with adding an Application.ProcessMessages.
(0001501)
user19
1969-12-31 17:33

STEPS TO REPRODUCE:
Load a large file such as CDSwNames.meg. Select an ML analysis and choose all sites.
It will take FOREVER to draw the initial screen.

(0001535)
agasky (reporter)
1969-12-31 17:33

When infering a maximum likelihood tree with a medium sized file (3mb) the Runtime Progress Dialog does not fully draw for at least 35 seconds. This issue is more pronounced when using a larger file (13mb) where the Runtime Progress Dialog isn't drawn for over 5 minutes. The issue seems to exist with all Maximum Likelihood analyses as they all share the ProcessSeqMLPhylogenyCommand procedure where the problem is called. I tracked the issue down to a function called SetParamsFromSeqs which was created by Tamura. The problem with SeqParamsFromSeqs is that it is not threaded and can take a significant amount of time to complete. I tried simply adding several Application.ProcessMessages statments but the SeqParamsFromSeqs function does not have "Application" within scope.

To Reproduce:
  Activate attached meg file
  Infer an ML tree


Call Stack:
  ProcessSeqMLPhylogenyCommand(dtdoMLTree, Self);
  CreateSubstitutionModel(MAI);
  Result.SetParamsFromSeqs(MAI.MySeqStrings); //This is the function that takes a long time and is not threaded

- Issue History
Date Modified Username Field Change
1969-12-31 17:33 user19 Note Added: 0001501
1969-12-31 17:33 user19 Note Edited: 0001501
1969-12-31 17:33 user19 Product Version 4.1-BETA =>
1969-12-31 17:33 user19 Description Updated
1969-12-31 17:33 user19 Description Updated
1969-12-31 17:33 user19 Description Updated
1969-12-31 17:33 user19 Additional Information Updated
1969-12-31 17:33 user19 Description Updated
1969-12-31 17:33 user19 Additional Information Updated
1969-12-31 17:33 user19 Description Updated
1969-12-31 17:33 user19 Description Updated
1969-12-31 17:33 user19 Description Updated
1969-12-31 17:33 user19 Description Updated
1969-12-31 17:33 user19 Description Updated
1969-12-31 17:33 user19 Assigned To user19 => agasky
1969-12-31 17:33 agasky Note Added: 0001535
2019-11-11 11:25 guest New Issue
2019-11-13 10:20 gstecher Status new => resolved
2019-11-13 10:20 gstecher Resolution open => no change required
2019-11-13 10:20 gstecher Assigned To => gstecher


Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker