Writing different data types to different subcases in H3D with Compose

I've discussed thoroughly with the teams responsible for results display in both Compose and HyperView and the behavior you are seeing is the expected way in which HyperView reads results in order to ensure efficient resource usage. Even though each datatype isn't present on each subcase, the structural hierarchy of the results files is what makes those results appear on the results explorer.

Unfortunately, there is no workaround, but I hope, however, that this is not issue that affects the functionality of any workflow and just a visual oddity.

Rafael

All comments

In my experience, if you define both data types before writing subcase B, both will be present.

However, you can write each datatype and subcase separately by closing the h3d file and opening it again. To open an existing file, use the "append" option. More details can be found here: createh3dfile.

Rafael

Hi Rafael,

this is how my code should work. But still, I get data types define in a previous subcase in a later one.

Here is a sample code:

fid = createh3dfile(path, 'append');



Name_Subcase = 'LoadCase: TEST';




tidx1 = createh3ddatatype(fid, 'TEST', 'scalar', 'elem', 'corners')


sidx1 = createh3dsubcase(fid, Name_Subcase, 'Result_Name_Text', [1.0]);



writeh3ddata(fid, sidx1, 1, tidx1, 0, 1, Data_Nodes(:,1), Data_Nodes(:,2:end)); %Nodalvalues




closeh3dfile(fid);








fid = createh3dfile(path, 'append');


Name_Subcase = 'LoadCase: TEST2';



tidx2 = createh3ddatatype(fid, 'TEST2', 'scalar', 'elem', 'corners'); %Nodalvalues


sidx1 = createh3dsubcase(fid, Name_Subcase, 'Result_Name_Text1', [1.0]);




writeh3ddata(fid, sidx1, 1, tidx2, 0, 1, Data_Nodes(:,1), 3*Data_Nodes(:,2:end)); %Nodalvalues

And this are the results in HyperView:

I define datatype TEST in subcase TEST and only datatype TEST2 in subcase TEST2. But still, both TEST and TEST2 are present in subcase TEST2.

QETU

Different_subcases_diferent_datatypes.oml

I've created a sample script which works for this:

close all, clear, clc

% Create file
fid = createh3dfile('.\test.h3d');

% Define first subcase and datatype
dtA = createh3ddatatype(fid, 'Datatype A', 'scalar', 'node');
sc1 = createh3dsubcase(fid, 'Subcase 1', [0]);
nodeIDs = 1:5';
D1 = ones(5,1);

% Define second subcase and datatype
dtB = createh3ddatatype(fid, 'Datatype B', 'scalar', 'elem');
sc2 = createh3dsubcase(fid, 'Subcase 2', [0]);
elemIDs = 1:10;
D2 = -ones(1,10);

% Write data for both
writeh3ddata(fid, sc1, 1, dtA, 0, 0, nodeIDs, D1);
writeh3ddata(fid, sc2, 1, dtB, 0, 0, elemIDs, D2);

% Close file
closeh3dfile(fid);

The output file has a subcase with datatype A defined, and another one with datatype B defined (a single datatype for each subcase). I'm attaching the script and output file for your reference.

Rafael

test.h3d

Hello @RSGarciarivas,

thanks for your script and the h3d. When I run your script on a sample model, i still have the same problem.

Not sure what is causing this… I am working with 2026. Maybe a different version will lead to different results?

Thank you for your help!

QETU

If you share the sample model here, I can have a better look.

Rafael

Writing_two_Subcases_with_one_Datatype.oml

Hi @RSGarciarivas,

i really apprechiate your help!

I have attached the files for you to have a better look.

QETU

test_Model_with_Results.h3d

test_Model_without_Results.h3d

I've reproduced this behavior on my side. I see that even if the CAE reader in Compose shows each datatype only in the correct subcase, both are shown in HyperView.

Let me discuss internally and I'll get back to you on whether there is a workaround for this.

Rafael

Unfortunately, there is no workaround, but I hope, however, that this is not issue that affects the functionality of any workflow and just a visual oddity.

Rafael