Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OverviewPyramid raises Zero Divide #735

Closed
seandenigris opened this issue Aug 3, 2015 · 6 comments
Closed

OverviewPyramid raises Zero Divide #735

seandenigris opened this issue Aug 3, 2015 · 6 comments

Comments

@seandenigris
Copy link
Contributor

Originally reported on Google Code with ID 735

Pharo image: Pharo1.3#13315
Virtual machine used: Pharo1.3
Platform Name: unix
Class browser used (if applicable): OBSystemBrowserAdaptor
Moose: 4.6_dev

Steps to reproduce:
#. open moose panel
#. select a model
#. visualize>>overview pyramid

Actual Result:
#. ZeroDivide
Expected Result:
#. the overview pyramid


* Type-Defect

Reported by vonbecmann on 2011-10-25 21:41:44


- _Attachment: [PharoDebug.log](https://storage.googleapis.com/google-code-attachments/moose-technology/issue-735/comment-0/PharoDebug.log)_
@seandenigris
Copy link
Contributor Author

Thanks. What was the input model?

Reported by tudor.girba on 2011-10-26 05:59:44

@seandenigris
Copy link
Contributor Author

see attached file

Reported by vonbecmann on 2011-10-26 12:58:16


- _Attachment: [data-exporter.mse](https://storage.googleapis.com/google-code-attachments/moose-technology/issue-735/comment-2/data-exporter.mse)_

@seandenigris
Copy link
Contributor Author

 I had the same problem when importing Monticello packages into moose... 
In my case there where 2 issues: the LOC (lines of code) and CALLS where not computed
(defaulting to 0) and they are used in for computing the pyramid -> thus ZeroDivide

Reported by ciprian.teodorov on 2011-10-26 16:52:13

@seandenigris
Copy link
Contributor Author

Reported by tudor.girba on 2011-11-16 09:19:44

@seandenigris
Copy link
Contributor Author

Overview Pyramid should be removed. In its current state, it does not provide too much
value.

Reported by tudor@tudorgirba.com on 2013-11-11 22:25:22

@seandenigris
Copy link
Contributor Author

I fixed overview pyramid to make it more robust. Still the code is in a deplorable state
and it should be rewrote almost entirely.

Reported by tudor@tudorgirba.com on 2013-12-05 06:59:07

  • Status changed: Fixed
  • Labels added: Component-Finder, Milestone-5.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant