Opened 14 years ago

Closed 13 years ago

#193 closed feature (fixed)

Complex constraints during fitting

Reported by: srkline Owned by: srkline
Priority: minor Milestone: Analysis 4.1 Release
Component: Analysis Keywords:
Cc: Blocking:


Can expressions be entered into the lo/hi table and parsed into meaningful constraints? Right now, a value "7" is parsed to Kn<7. Entering K1+K2 should parse to Kn<K1+K2. A preview would help...

Change History (4)

comment:1 Changed 14 years ago by srkline

this does work.

It is somewhat confusing, however, to think about which one parses to a ">" and which one to a "<", but it's not too bad.

Biggest problem is figuring out how to get feedback about the constraints, and which ones have been run up to an edge, or worse, which ones were violated.

comment:2 Changed 14 years ago by srkline

Also, be careful if we ever decide to make the fit functions threadsafe. Then the textwave of contraints can't be used. It'll need to be parsed into a constraint matrix+vector. See the Curve fitting help for the warning and details.

comment:3 Changed 13 years ago by srkline

  • Milestone changed from Analysis Wish List to Analysis 4.1 Release

comment:4 Changed 13 years ago by srkline

  • Resolution set to fixed
  • Status changed from new to closed

Help file has been updated to show how these constraints can be entered (with an example).

video help will be added in the future.

Note: See TracTickets for help on using tickets.