Opened 2 weeks ago
Last modified 11 days ago
#2968 accepted feature request
Add a new formatter for symbolic expressions, which produces an infix expression as well as a list of all coefficient values
Reported by: | chaider | Owned by: | chaider |
---|---|---|---|
Priority: | medium | Milestone: | HeuristicLab 3.3.16 |
Component: | Problems.DataAnalysis.Symbolic | Version: | branch |
Keywords: | Cc: |
Description
Representation of coefficients of the mathematical representation for solution models. Display coefficients as strings to be able to copy/paste values into other programs for further analysis.
e.g.
Mathematical Representation:
Y = (c0 * x + c1 * y + c2 * z)
Coefficients:
c0 = -0.03129
c1 = 1.5293
c2 = -0.93221
Change History (8)
comment:1 Changed 2 weeks ago by chaider
- Summary changed from Infix Symbolic String Formatter to Add a new formatter for symbolic expressions
comment:2 Changed 2 weeks ago by chaider
- Status changed from new to accepted
- Summary changed from Add a new formatter for symbolic expressions to Add a new formatter for symbolic expressions, which produces an infix expression as well as a list of all coefficient values
comment:3 Changed 2 weeks ago by chaider
comment:4 Changed 2 weeks ago by chaider
r16337 Added Problems.DataAnalysis.Symbolic
comment:5 Changed 2 weeks ago by chaider
r16338 Added references to projects and added build events.
comment:6 Changed 13 days ago by chaider
r16339: Added infix expressen string formatter class
comment:7 Changed 13 days ago by chaider
r16340 Changed formating of constant list
comment:8 Changed 11 days ago by mkommend
Review Comments
Visual representation looks very good!
InfixStringFormatter
- I personally do not like the file and class name. Please think of a better one that indicates the differences between both infix formatters
- Do constants and constants counter have to be member variables. Would it be sufficient to declare them in the format method
- Why are the maximum digits dependent on the number of constants (line 42)?
- GetDigits lines 180 & 182 are obsolete in my opinion. It does exactly the same as line 183.
- Can these functionality be integrated in the default infix formatter so that fewer / no code is duplicated?
Note: See
TracTickets for help on using
tickets.
r16336 added new branch