Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

postprocessing variables name parts get parsed instead of whole variable names #392

Open
stephenwhitmarsh opened this issue Apr 20, 2022 · 0 comments

Comments

@stephenwhitmarsh
Copy link
Member

stephenwhitmarsh commented Apr 20, 2022

When an earlier defined variable name is (the first?) part of subsequent variable name definition, it replaces that overlapping part with the value of the earlier variable. Switching the order removes this issue. I am not sure this has to do with the underscore, but it is unexpected. For example, the following configuration in postprocessing.ini:

[input]
rms1=rms.channel1
rms1_min=rms.channel1.min_att
rms1_max=rms.channel1.max_att

[output]
post.rms1 = ((rms1 - rms1_min * 0.5) / (max(rms1_max, rms1*1.1) - rms1_min * 0.5))

results in (note the NUMBER_min and NUMBER_max):

ERROR: postprocessing: Error in evaluation: post.rms1 = ( ( 18.448567988897565 - 18.448567988897565_min * 0.5 ) / ( max( 18.448567988897565_max , 18.448567988897565 * 1.1 ) - 18.448567988897565_min * 0.5 ) )

This is resolved when reordering the input variable names:

[input]
rms1_min=rms.channel1.min_att
rms1_max=rms.channel1.max_att
rms1=rms.channel1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant