SweepFormula: add data as variables

[ukos-git]

Similar to JSON logic, the data should get separated from the operations. This ensures that we do not call the getter two times if for example, calculating with it.

derivative(data(cursors(a,b), channels(AD), sweeps())) * data(cursors(a,b), channels(AD), sweeps())

will then reduce to

derivative(var0)*var0

with the data object

var0=data(cursors(a,b), channels(AD), sweeps());

It can also mean that the functions are a lot easier to read. and you can name the data.

To get to that point, string values need to get checked if a variable is registered for them. Probably related to #274

I don't see significant problems implementing that.

[ukos-git]

http://jsonlogic.com/

[t-b]

• data will be defined in separate notebook
• will make it faster

[ukos-git]

From the json logic documentation about the var operation:

logic:

{
  "and": [
    {
      "<": [
        {
          "var": "temp"
        },
        110
      ]
    },
    {
      "==": [
        {
          "var": "pie.filling"
        },
        "apple"
      ]
    }
  ]
}

data:

{
  "temp": 100,
  "pie": {
    "filling": "apple"
  }
}

should return true aka 1

[t-b]

Example:

currSel = select(channels(AD9), [31,33,34], all)
myrange = [2000,4000]
kernel = epspKernel($myrange, $currSel)

epspKernel($myrange, $currSel)
and
epspStats($myrange, $currSel, tau, accept, hist)

Properties:

• Needs to be known across all with and and parts
• No partial expression support
• Each entity is known and can be used on the next line

Implementation idea:

• Evaluate the A = ... lines not in the parser but separate
• Assignments stop on the first non-empty/non-comment line which are not an assignment
• Store results in wave ref waves globally, use separate text wave for entity name (lhs of =)
• Only allow strict object names for entity names (see IsValidObjectName)
• Teach the parser that $ is an accepted character in strings
• The executor looks up strings starting with $ in global wave ref wave. That also means that all operations know nothing about those entities.
• When encountering unknown $abcd entities we abort with SF_Assert

Limitations:

• This does disallow starting a string with $, i.e. $abcd or "$efgh"

Related idea:

• Only allow strict object names for operation names, see SF_FormulaParser line 526, (tempPath += SF_EscapeJsonPath(buffer[0, parenthesisStart - 1]))