As your code is not contained in a class or function it is expecting those variables to be constants and as such they should be uppercase.
You can read PEP8 for further information.
EDIT: As others have mentioned, pylint expects that global variables should be UPPERCASE. If the warnings really bother you, you can circumvent them by wrapping small snippets like this in a main()-function and then use the if __name__ == "__main__"-convention. Or if you care, you can modify the regular expressions that pylint uses to validate variable names.
From the developers of Pylint.
In this case Pylint is telling me that those variables appear to be constants and should be all UPPERCASE. This rule is in fact a naming convention that is specific to the folks at Logilab who created Pylint. That is the way they have chosen to name those variables. You too can create your own in-house naming conventions but for the purpose of this tutorial, we want to stick to the PEP-8 standard. In this case, the variables I declared should follow the convention of all lowercase. The appropriate rule would be something like: "should match [a-z_][a-z0-9_]{2,30}$". Notice the lowercase letters in the regular expression (a-z versus A-Z)
You can test it by running:
pylint --const-rgx='[a-z_][a-z0-9_]{2,30}$' x.py
I fixed the issue by changing from csh to bash, removing set echo (caused some weird issue by making all input variables into "echo")and changing from $(()) to $().
the $(( expr )) syntax is used for calculations hence the confusing message.
ex: echo $((4+4)) yields 8
you want to evaluate the result of a command, simple parenthesis will do:
To_Start=$(grep -n -m 1 "HR${4}" Tossed/length${1}/TL${1}D2R${2}-${3}TT.txt | cut -d : -f 1)
Simple reproducer to prove my point:
To_Start=$(echo a:b | cut -d : -f 1)
echo $To_Start
yields:
a