# Can ParaView be case insensitive for variables?

**URL:** https://discourse.paraview.org/t/can-paraview-be-case-insensitive-for-variables/11621
**Category:** ParaView Support
**Created:** [March 14, 2023, 2:21am UTC](https://discourse.paraview.org/t/can-paraview-be-case-insensitive-for-variables/11621 "2023-03-14T02:21:59Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [March 14, 2023, 2:21am UTC](https://discourse.paraview.org/t/can-paraview-be-case-insensitive-for-variables/11621/1 "2023-03-14T02:21:59Z")

</div>

Hi ParaViewers,  
Is there a way to make ParaView case insensitive for variables coming out of Exodus datasets? An example would be my user wants to have v\_x, V\_Y and v\_Z all be part fo the same vector.

One Idea I had is the python calculator. Anyone tried that?

Thanks,  
Alan

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 14, 2023, 7:02am UTC](https://discourse.paraview.org/t/can-paraview-be-case-insensitive-for-variables/11621/2 "2023-03-14T07:02:30Z")

</div>

Calculator and PythonCalculator definitely can do that for you, and much more.

---

<div class="post-metadata">

### Author: ![ajsters](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/a/48db29/32.png) [@ajsters](https://discourse.paraview.org/u/ajsters)
#### Post date: [March 14, 2023, 2:49pm UTC](https://discourse.paraview.org/t/can-paraview-be-case-insensitive-for-variables/11621/3 "2023-03-14T14:49:51Z")

</div>

Do you have any examples of Calculator treating input variables as case insensitive? When I try (e.g. loading ‘rotation\_xx’ when ‘rotation\_XX’ exists), it errors out with the variable not found.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 14, 2023, 2:51pm UTC](https://discourse.paraview.org/t/can-paraview-be-case-insensitive-for-variables/11621/4 "2023-03-14T14:51:41Z")

</div>

That is not what I meant at all.

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [March 14, 2023, 4:28pm UTC](https://discourse.paraview.org/t/can-paraview-be-case-insensitive-for-variables/11621/5 "2023-03-14T16:28:00Z")

</div>

Hi Mathieu,  
Maybe I should have clarified to say I am looking for a way to automatically have ParaView case insensitive. In other words, have t and T be seen as the same variable, without the user having to explicitly apply the calculator for the conversion.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 14, 2023, 4:31pm UTC](https://discourse.paraview.org/t/can-paraview-be-case-insensitive-for-variables/11621/6 "2023-03-14T16:31:36Z")

</div>

That sounds very hard to do correctly. Think like the “AutoConvertProperties” and all the issues that arise with it.

---

<div class="post-metadata">

### Author: ![patchett2002](https://discourse.paraview.org/user_avatar/discourse.paraview.org/patchett2002/32/235_2.png) [@patchett2002](https://discourse.paraview.org/u/patchett2002)
#### Post date: [March 14, 2023, 4:55pm UTC](https://discourse.paraview.org/t/can-paraview-be-case-insensitive-for-variables/11621/7 "2023-03-14T16:55:54Z")

</div>

I think making all variables case insensitive would break more than it fixes. My users are typically supercomputer users that understand the difference between upper and lower case to be different and have machinations that leverage that. That said, I could imaging some settings in say readers and certainly within python calculators and filters where a user says (checks a box in advanced settings) “make all scalar/vector names lower case”.  
OR  
yet another filter → “make all array names lower”  
OR  
in Pass Arrays Filter , allow the renaming of the arrays that get passed, which would make it easier, and convenient. I’ve certainly had to rename arrays in the past, and have to look up how to do each time. A GUI mechanism with click, click, click would be nice and pass arrays might be the right way/place to do it?

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [March 14, 2023, 5:13pm UTC](https://discourse.paraview.org/t/can-paraview-be-case-insensitive-for-variables/11621/8 "2023-03-14T17:13:50Z")

</div>

Agreed. I started my discussion with my user with “that’s a really bad idea, but if you want to,…” I’m thinking the answer without any additional coding would be one of the python filters. Alternatively, teach users the difference between lower case and upper case? 🙂

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [March 20, 2023, 1:50am UTC](https://discourse.paraview.org/t/can-paraview-be-case-insensitive-for-variables/11621/9 "2023-03-20T01:50:31Z")

</div>

> [@wascott](#):
>
> my user wants to have v\_x, V\_Y and v\_Z all be part fo the same vector

Your user can use the **Merge Vector Components** to merge arbitrary arrays, including this example.
