Add support for variable scoping

[benkrikler]

I've started looking into using this package for a project I'm working on. We'll want to be able to specify branches which might be nested within our trees, eg. branch.sub_branch. I've tested this briefly with version 0.0.7 of formulate though and I see that such variables cannot be identified:

$ python -m formulate --from-numexpr 'branch.sub_branch < 4' --variables
ERROR:formulate:TODO TRACEBACK: ('branch.sub_branch < 4', 6, 'Expected end of text')
ERROR:formulate:Error parsing: branch.sub_branch < 4
ERROR:formulate:                     ▲
ERROR:formulate:                     ┃
ERROR:formulate:                     ┗━━━━━━ Error here or shortly after

Would it be possible to add support for this? PyParsing has a specific helper method which might be useful here, delimitedList. I think the easiest for the user is to return a single variable in this case branch.sub_branch in the example above. That might mean just including the . in the definition of the Word for Variables?

[chrisburr]

Yes, I definitely want to add support for this!

I don't use files like this very often, would you be able to share an example file? You can send it to me privately if you'd prefer by emailing me at christopher.burr with the domain being cern.ch.

[benkrikler]

The samples I'm developing against are a bit private atm I'm afraid, but I think the mc10event.root file in uproot's testing samples is a good equivalent for what I'm looking at:
https://github.com/scikit-hep/uproot/blob/master/tests/samples/mc10events.root. Would that work for you?

[chrisburr]

Thanks for file (and the delimitedList suggestion), I've added basic support now in v0.0.8. The example you gave now looks like this:

$ python -m formulate --from-numexpr 'branch.sub_branch < 4' --variables
branch.sub_branch

I don't work with files like this very often so please open issues if you run into more limitations. 😄

[eduardo-rodrigues]

Same comment made at #22 - example above worth having in the README. Maybe use the file above for a test?

[benkrikler]

Thanks for such a speedy implementation, Chris!

[marinang]

Hi I have a similar problem with with variables that have dot "." inside. See

As you can see, this is done with the last version of formulate, i.e v0.08.

The variables that bring problem are the isolation variables header_0.30_cc_asy_PT where 0.30 stands for the cone radius, this variables is automatically created by a LHCb tupletool.

An additional concern that I have, is how then the numpexpr conversion will be done?

[jonas-eschle]

We've just released 1.0: https://github.com/scikit-hep/formulate/releases/tag/v1.0.1

formulate is agnostic to the name, so we can now implement downstreams access to elements (as this requires a bit more handling for the different backends, I think @ariostas will look into this for uproot)

Glad to have feedback and feel free to close if this resolves the issue