Unexpected plot shown by ParaView Catalyst on using Rectilinear Conduit blueprint

In Situ Support
2

I used the debugging and info to get the following. This most likely seems to be something weird going on when Conduit rectilinear mesh blueprint is processed by ParaView Catalyst to generate the rendered images.

// print for debugging purposes, if needed
conduit_node_print(catalyst_exec_params);

// print information with details about memory allocation
conduit_node* info = conduit_node_create();
conduit_node_info(catalyst_exec_params, info);
conduit_node_print(info);
conduit_node_destroy(info);

Proc 0:

catalyst: 
  state: 
    timestep: 0
    time: 0.0
  channels: 
    grid: 
      type: "mesh"
      data: 
        coordsets: 
          coords: 
            type: "rectilinear"
            values: 
              x: [0.0, 0.25, 0.5]
              y: [0.0, 1.0, 1.5]
              z: [0.0, 0.0]
        topologies: 
          mesh: 
            type: "rectilinear"
            coordset: "coords"
        fields: 
          density: 
            association: "element"
            topology: "mesh"
            volume_dependent: "false"
            values: [0.0, 0.05, 0.5, 1.0]


mem_spaces: 
  0x55c6974884e0: 
    path: "catalyst/state/timestep"
    type: "allocated"
    bytes: 8
    allocator_id: 0
  0x55c697525e80: 
    path: "catalyst/state/time"
    type: "allocated"
    bytes: 8
    allocator_id: 0
  0x55c697541ef0: 
    path: "catalyst/channels/grid/type"
    type: "allocated"
    bytes: 5
    allocator_id: 0
  0x55c697488a00: 
    path: "catalyst/channels/grid/data/coordsets/coords/type"
    type: "external"
  ... ( skipped 6 children )
  0x55c6974a2c70: 
    path: "catalyst/channels/grid/data/fields/density/topology"
    type: "external"
  0x55c6974a2dd0: 
    path: "catalyst/channels/grid/data/fields/density/volume_dependent"
    type: "external"
  0x7ffc5118ba30: 
    path: "catalyst/channels/grid/data/fields/density/values"
    type: "external"
total_bytes_allocated: 21
total_bytes_mmaped: 0
total_bytes_compact: 167
total_strided_bytes: 167

Proc 1:

catalyst: 
  state: 
    timestep: 0
    time: 0.0
  channels: 
    grid: 
      type: "mesh"
      data: 
        coordsets: 
          coords: 
            type: "rectilinear"
            values: 
              x: [0.5, 0.75, 1.0]
              y: [0.0, 1.0, 1.5]
              z: [0.0, 0.0]
        topologies: 
          mesh: 
            type: "rectilinear"
            coordset: "coords"
        fields: 
          density: 
            association: "element"
            topology: "mesh"
            volume_dependent: "false"
            values: [0.1, 0.2, 2.0, 3.0]


mem_spaces: 
  0x555980ac0c40: 
    path: "catalyst/state/timestep"
    type: "allocated"
    bytes: 8
    allocator_id: 0
  0x555980ad9db0: 
    path: "catalyst/state/time"
    type: "allocated"
    bytes: 8
    allocator_id: 0
  0x555980ad9d70: 
    path: "catalyst/channels/grid/type"
    type: "allocated"
    bytes: 5
    allocator_id: 0
  0x555980ad9cb0: 
    path: "catalyst/channels/grid/data/coordsets/coords/type"
    type: "external"
  ... ( skipped 6 children )
  0x555980ac1a90: 
    path: "catalyst/channels/grid/data/fields/density/topology"
    type: "external"
  0x555980ac1ab0: 
    path: "catalyst/channels/grid/data/fields/density/volume_dependent"
    type: "external"
  0x7fff567bec20: 
    path: "catalyst/channels/grid/data/fields/density/values"
    type: "external"
total_bytes_allocated: 21
total_bytes_mmaped: 0
total_bytes_compact: 167
total_strided_bytes: 167

After further testing, I found out that the Catalyst generated rendering is independent of whatever y values I pass to using Conduit rectilinear mesh blueprint. This happens only when multiple processors are involved. The way Catalyst is functioning is that it is treating the y direction to be same as the x direction irrespective of what y values are passed.