OMNeT++/OMNEST Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000800OMNeT++simulation kernelpublic2014-12-12 16:352014-12-12 16:36
Reportertill 
Assigned To 
PrioritylowSeverityfeatureReproducibilityhave not tried
StatusnewResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0000800: @range property
DescriptionWe are currently doing a lot of range checks of parameters in the handleParameterChange method. This requires some code but helps to prevent strange results due to wrong parameters.

I just wanted to introduce a new property in our model called @range(min,max) (maybe with two optional parameters whether the lower and upper bounds are included in the range).
Then in the handleParameterChange I wanted to get the values from the property. This way the upper and lower bounds would be nicely documented in the ned!

Then I thought, this should be a simulation core feature!!! The simulation core could do the range checks then, this would allow the developers to save the code for range checks and the ini editor could check prior runtime for parameters that are out of bounds. And ned-doc could show the range!

In my eyes this would be very very very useful. And yould improve models a lot (A lot of models don't do range checks on the parameters!). If I'm not alone with this wish, I am happy to help implementing that for OMNeT++ 4.7. Comments appreciated! :)

Best regards
Till
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2014-12-12 16:35 till New Issue
2015-10-12 09:28 ammmar1988 Issue cloned: 0000868


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker