search

visit-dav / visit

VisIt - Visualization and Data Analysis for Mesh-based Scientific Data
https://visit.llnl.gov
BSD 3-Clause "New" or "Revised" License
434 stars 112 forks source link

We should fix misleading warning message. #13264

Closed brugger1 closed 3 years ago

brugger1 commented 3 years ago

Steve Langer was running VisIt and it output the message below. He found it confusing since it said the behavior that it was warning about was going to change in version 2.13 and he was running 3.1.4. We should remove the part of the message that says the behavior will change in version 2.13.

It also seems like the message starts in the middle and when it gets to the end it continues at the beginning of the message. This may just be some odd behavior in how errors eventually make it to the terminal.

"VISIT_FORCE_SPECULATIVE_EXPRESSION_GENERATION"

set. Be aware that doing so will likely result in sluggish GUI performance. If you need one or more of the expressions VisIt's speculative expression generation process provides and are unwilling or unable to manually create the expression(s) you need, you have no choice in this version of VisIt except to override this behavior and suffer any GUI performance issues. Unfortunately, if you are running in client-server mode, you will have to take action to set this enviornment variable on both the server and client machines. This will only be necessary in VisIt version 2.12.3. An entirely different mechanism for controlling this behavior will be introduced in 2.13. VisIt: Warning - Due to the large number of variables, 1054, in this database, VisIt has automatically disabled speculative expression generation of ALL forms (e.g. vector-magnitude, mesh-quality, time-derivative, operator-created) because the large number of expressions bogs down GUI performance. You may override this behavior by exiting VisIt and restarting with the environment variable...

brugger1 commented 3 years ago

It looks like this behavior is controlled by:

Environment::exists(md->GetSEGEnvVarName())

Was the possible intent that in the future this be controlled by a setting in the GUI, perhaps a preference?

markcmiller86 commented 3 years ago

Was the possible intent that in the future this be controlled by a setting in the GUI, perhaps a preference?

Kinda...the correct solution is to allow the use to push a button to generate desired groups of expressions if needed as well as to have a setting that does it automatically.

brugger1 commented 3 years ago

We should just remove the version specific comment.