Order of data unclear

[ngodber]

I'm attempting to access and modify the cell values for a BlockModel using geoh5py. Of course, data are stored as a vector. The documentation is unclear as to the ordering of the data values with the only reference I can find being https://mirageoscience-geoh5py.readthedocs-hosted.com/en/release-0.10.0/content/api/geoh5py.objects.html. I've attempted using simply numpy reshape whilst passing the block_model.shape parameter and the results seem non-sensical. I'm thus guessing that the ordering of the values conforms to UBC standard, e.g. https://giftoolscookbook.readthedocs.io/en/latest/content/fileFormats/modelfile.html . Is this correct?

[domfournier]

To be addressed on GEOPY-1950

[ngodber]

After our chat last week the confusion has unfortunately continued. I'll DM you a link to the project that I'm using that, combined with attached workbook, lets you recreate once I'm seeing. To test I'm setting the top layer to 50. If I use flatten() then EW slices are zero'd (!!). If U se flatten ('F") then the top layer is set to 50 but the remainder of the data goes haywire. I'm truly stumped as to what is going on.

working.zip

[domfournier]

You almost had it.
First to reshape 3D

distance.reshape((model.shape[2],model.shape[0],model.shape[1]), order="F")

Then back to flatten

distance.flatten(order="F")

Fortran in, fortran out.

[ngodber]

Ah, clear. The test object was such that it was non-obvious the first reshape wasn't behaving expected! Thanks for the fast response.

…

On Tue, 21 Jan 2025 at 14:40, domfournier ***@***.***> wrote: You almost had it. First to reshape 3D distance.reshape((model.shape[2],model.shape[0],model.shape[1]), order="F") Then to flatten back distance.flatten(order="F") Fortran in, fortran out. — Reply to this email directly, view it on GitHub <#689 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC2JLXVQZ4PCWNCJZTMKVT32LXFU7AVCNFSM6AAAAABVIQFWEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBTGY2DEMJWGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>