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

Exercise plan for AlarmPP model #89

Closed
bandurvp opened this issue Apr 10, 2017 · 6 comments
Closed

Exercise plan for AlarmPP model #89

bandurvp opened this issue Apr 10, 2017 · 6 comments
Assignees
Milestone

Comments

@bandurvp
Copy link
Contributor

bandurvp commented Apr 10, 2017

Devise an exercise plan, written in VDM, that exercises execution time and memory usage. This night be split up into:

  1. A validation plan, that ensures that the generated model behaves as it should.
  2. A (potentially independent) exercise plan.
@bandurvp bandurvp added this to the v0.1.6 milestone Apr 10, 2017
@bandurvp bandurvp self-assigned this Apr 10, 2017
@bandurvp
Copy link
Contributor Author

I have discovered a useful feature of VDMTools. Basic values at least, such as bool, can be pretty-printed in the usual C++ way cout << var;. I have used this in the validation plan to confirm that the VDMTools generated code works as expected.

@peterwvj
Copy link
Member

Cool. I actually thought we tested that -- perhaps we only tried it on user-defined data types :)

@bandurvp
Copy link
Contributor Author

An update, an initial stress test runs correctly and without memory leaks. The test model code is in the SVN in the WellFoundedCG paper folder.

@bandurvp
Copy link
Contributor Author

@peterwvj , I'm very happy to report that the first test, that in which I check whether the generated code actually performs correctly, shows code from VDM2C to use almost half the total memory that code from VDMTools does!

@peterwvj
Copy link
Member

Awesome, Victor :) That's very promising. Thanks for letting me know!

@peterwvj peterwvj modified the milestones: v0.1.6, v0.1.8 May 1, 2017
bandurvp pushed a commit that referenced this issue May 10, 2017
bandurvp pushed a commit that referenced this issue May 10, 2017
bandurvp pushed a commit that referenced this issue May 10, 2017
bandurvp pushed a commit that referenced this issue May 11, 2017
bandurvp pushed a commit that referenced this issue May 16, 2017
bandurvp pushed a commit that referenced this issue May 26, 2017
bandurvp pushed a commit that referenced this issue Jun 1, 2017
bandurvp pushed a commit that referenced this issue Jun 2, 2017
bandurvp pushed a commit that referenced this issue Jun 2, 2017
bandurvp pushed a commit that referenced this issue Jun 2, 2017
-  AlarmPP model now can be inspected using valgrind's massif.
-  Addresses #89.
peterwvj added a commit that referenced this issue Jun 8, 2017
bandurvp pushed a commit that referenced this issue Jun 8, 2017
@peterwvj peterwvj modified the milestones: v0.1.8, v0.1.10 Jul 1, 2017
@peterwvj peterwvj modified the milestones: v0.1.10, v0.1.12 Aug 10, 2017
@peterwvj peterwvj modified the milestones: v0.1.12, v0.1.10 Aug 10, 2017
@peterwvj peterwvj modified the milestones: v0.1.12, v0.1.14 Sep 11, 2017
@peterwvj peterwvj modified the milestones: v0.1.14, v0.1.16 Sep 18, 2017
@peterwvj peterwvj modified the milestones: v0.1.16, v0.1.18 Oct 4, 2017
@peterwvj peterwvj modified the milestones: v0.2, v0.2.2 Feb 14, 2018
@peterwvj
Copy link
Member

I think this can be closed now.

@peterwvj peterwvj modified the milestones: v0.2.2, v0.2 Feb 14, 2018
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

2 participants