Resolve refresh boundary issue in 2d integration
Framework for numerical computations, data analysis and visualisation
Brought to you by:
numere
Previous tickets had to disable this feature. Find a possibility to re-enable it using runtime-efficient solutions.
A future-proof implementation would be as follows:
Interval data type, which contains methods for finding dependencies (e.g. bool Interval::contains(const std::string& sVarName)) and methods for accessing samples (e.g. double Interval::getSample(size_t nSample, size_t nSamples = 100)) as well as sample setter and getter and a std::string Interval::name to get and change the interval nameInterval data type should be created in a fashion to support data types as intervals in the futureInterval data type shall provide a Interval::refresh() function, to recalculate itselfIntervalSet data type, which will contain all defined intervalsIntervalSet to std::vector<double> to maintain backwards compatibility where necessaryCommandLineParser shall only return an IntervalSet to force dropping backwards compatibilityintegrate statements to the SW tests and used the new interval decoding logic in various locations.Automatic SW tests were reviewed and re-run without any deviation.
Anonymous
Diff:
Diff:
Diff:
Related
Commit: [r901]
Diff: