Question about settings on rescale

ParaView Support
1

Hello,

I am trying to create de default settings Paraview-UserSetting.json with some options I need but it does not seem to take it into account.

I add the following line in my setting files:

        "settings" :
        {
                "GeneralSettings" :
                {
                        "AutomaticRescaleRangeMode" : 4,
                        "BlockColorsDistinctValues" : 15,
                        "DefaultTimeStep" : 2,
                        "SelectOnClickInMultiBlockInspector" : 0
                }
        }

I closed paraview and relaunched it, load the example database can.ex2 and I have this window:

Capture d’écran de 2022-10-21 17-51-14
Capture d’écran de 2022-10-21 17-51-142560×1440 393 KB

We can see that there is only 12 colors in my categorical colors (I thought I tell paraview I wanted 15) and the default rescale mode is again “Grow and Update on Apply”.

However, the select on click in the multiblock inspector and the default timestep are well applied.

Why some parameters are ignored from my config file ?

Thanks for your help,
Eloïse

2

Up: Anyone could help me to have a valid configuration file ? :frowning:

3

Hi @Eloise

I’m a bit confused by the question, could you provide clear steps to reproduce the issue ?

Best,

4

I want a Paraview-UserSetting.json which set the automatic rescale to “Clamp and Update everytimestep” by default.
I wrote the config file above (with "AutomaticRescaleRangeMode" : 4)

However, when I open paraview, the default mode is always “Grow and update on ‘Apply’”.

Others settings in this file is applied (last time by default), but not the rescale mode.

5

There is no such settings, here is how to do it:

{
  "lookup_tables" : 
  {
    "PVLookupTable" : 
    {   
      "AutomaticRescaleRangeMode" : 3 
    }   
  }
}
6

Ok, so this wasn’t an general setting as I thought but something more hidden =)
Thank you, it works =)

1 Like
7

Hi Eloise,
We have been debating the Automatic Rescale setting for years, and keep believing that although it gives pretty movies, it is actually confusing to have the min and max updated every timestep. What is the usecase you have, and why do you need to update the min and max every timestep?
Thanks for the insite,
Alan

8

Hello, It’s quite simple: some of my field begin to the max value at initial time andd the become smaller. “Grow and update” keeps me the biggest scale and I could not see changes in time: In the can.ex2 example, use the “grow and update” rescale with the ACCL field results in a all red figure during all timestep