Split grid/geometry and properties EPC


I am trying to export a case as split geometry (grid topological and any grid related property info e.g. cell IDs etc) and properties (e.g. cell and connection model properties) EPC/H5 file combos. It is to be noted that all the properties are supported on the same grid (cell properties on the grid representation, connection properties on the connection set representation). But using C++ APIs it is always throwing an exception when trying to serialize the props EPC.

For additional detail, my grid is of type UnstructuredGridRepresentation, connection is of type GridConnectionSetRepresentation as usual. The two H5 files appear to be generated OK and if I comment out the serialize call to the properties EPC, it runs through OK as well, and unified EPC export has always been working OK for me. So I wonder if this type of split export scenario is even supported in that version (it seems that one problem could be the memory management of same grid and connection set representation across two EPC?) and perhaps resolved in later versions?

Appreciate any thoughts on this.


Update - I just tried with createPartialUnstructruedGridRepresentation and still see the same behavior (exception when trying to serialize the properties EPC). My current workflow is as follows:

Main implementation that creates and populates (from input data) the two EPC documents (grid, properties) and their corresponding H5 bulk data using Fesapi APIs, are inside a dedicated class. Then after they have been created and populated, in the driving application I call to serialize (following the outline in example.cpp):

        EpcDocument* props_ptr = converter.get_props();
        if (!props_ptr)
          return false;
        EpcDocument* ptr = converter.get();
        if (!ptr)
          return false;

In the above snippet, tested also various ordering (e.g. first grid EPC, then closing it, then properties EPC, or reversing the order etc); commenting all the references to props_ptr in the above, or even commenting only the call to properties EPC props_ptr->serialize() allows it to run through without the exception.