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

Export DB is refusing to export several of my variables defined with expressions... only via the CLI #19512

Open
JustinPrivitera opened this issue May 14, 2024 · 0 comments
Assignees
Labels
bug Something isn't working impact medium Productivity partially degraded (not easily mitigated bug) or improved (enhancement) likelihood medium Neither low nor high likelihood reviewed Issue has been reviewed and labeled by a developer
Milestone

Comments

@JustinPrivitera
Copy link
Member

JustinPrivitera commented May 14, 2024

Describe the bug

Some of my user-defined expressions fail to be exported using Blueprint export via the CLI. When I export using the GUI, it works fine.

These same expressions also always fail to be exported using Silo.

Helpful additional information

  • Did VisIt crash: no
  • Did you get wrong results: yes

To Reproduce

I have created several variables:

	# define some variables for export
	DefineVectorExpression("logical_zoneid", "logical_zoneid(hydro_mesh)")
	DefineScalarExpression("i", "logical_zoneid[0]")
	DefineScalarExpression("j", "logical_zoneid[2]")

When I export using the GUI and request i and j, it works as I would expect. But using the CLI, they do not get exported no matter what I try:

        e = ExportDBAttributes()

        # this first option is what I want
	# e.variables = tuple(akap_names) + tuple(ekap_names) + tuple(vemis_names) + ('den', 'tmat', 'i', 'j')

        # but even doing this second option does not lead to either of the variables being exported
	e.variables = ('i', 'j')

Expected behavior

I expect i and j to be exported.

Desktop

  • OS and version: RZ
  • VisIt Version: 3.4.1, 3.3.3
  • Server info (if applicable):
@JustinPrivitera JustinPrivitera added bug Something isn't working likelihood medium Neither low nor high likelihood impact medium Productivity partially degraded (not easily mitigated bug) or improved (enhancement) labels May 14, 2024
@cyrush cyrush added this to the 3.4.3 milestone Jun 11, 2024
@cyrush cyrush added the reviewed Issue has been reviewed and labeled by a developer label Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working impact medium Productivity partially degraded (not easily mitigated bug) or improved (enhancement) likelihood medium Neither low nor high likelihood reviewed Issue has been reviewed and labeled by a developer
Projects
None yet
Development

No branches or pull requests

2 participants