Hi HyeonYong, My apologies for not replying sooner. I've looked at the data, and yup, it looks like there are some non UTF-8 characters. This is the attribute "ChimieLabels" and they don't show up as UTF-8 or UTF-16. Here is the raw bytestring: b'Fe,Mg,O,S,Zn,Sr,Y,Ba,Eu,Metals, \x13Y\xd8\xa4\x86w\xa3?\xd8\x859q\xc0u\xb3?(\xc2?i\xf7-\xbd?}\x9a\x9c#4r\xc3?\xc2^\xe1\x8b\x89L\xc8?]\xf0\xad\xf3\xfb%\xcd?+\xab\x99\xb0E\xff\xd0?9\xf6I\xed\x1bk\xd3?W\xab\xf1\xb2\x80\xd6\xd5?\x19G\x93\x04tA\xd8?=\xeb)\xe5\xf5\xab\xda?Sd\xa9W\x06\x16\xdd?\xa2\'\xfe^\xa5\x7f\xdf?/\xa9\x06\x7fi\xf4\xe0?\x99W\xda\x9b\xc7(\xe2?\xf9We\x07\xed\\\xe3?M:\x0f\xc3\xd9\x90\xe4?\xa2\xe3;\xd0\x8d\xc4\xe5?"\x90K0\t\xf8\xe6?\xd3\xd1\x9a\xe4K+\xe8?\xbb\x92\x82\xeeU^\xe9?\xda\x12XO\'\x91\xea?\x02\xebl\x08\xc0\xc3\xeb?\xb8\x0b\x0f\x1b \xf6\xec?P\xbd\x88\x88G(\xee?C\xa2 R6Z\xef?=\xda\x8c<\xf6E\xf0?\xc0\xa4Y\xff\xb4\xde\xf0?y\x87\x14rWw\xf1?<\x87Y\x95\xdd\x0f\xf2?\xad\xd5\xc2iG\xa8\xf2?\xb2\xd2\xe8\xef\x94@\xf3?\x9d\x0bb(\xc6\xd8\xf3?.<\xc3\x13\xdbp\xf4?\x9bN\x9f\xb2\xd3\x08\xf5?+[\x87\x05\xb0\xa0\xf5?\xd9\xa9\n\rp8\xf6?\x1c\xb1\xb6\xc9\x13\xd0\xf6?#\x17\x17<\x9bg\xf7?\x8b\xb1\xb5d\x06\xff\xf7?A\x86\x1aDU\x96\xf8?\x0c\xcb\xcb\xda\x87-\xf9?d\xe6M)\x9e\xc4\xf9?\x94o#0\x98[\xfa?\x01/\xcd\xefu\xf2\xfa?\\\x1e\xcah7\x89\xfb?\xf9h\x97\x9b\xdc\x1f\xfc?\x86l\xb0\x88e\xb6\xfc?\xb1\xb8\x8e0\xd2L\xfd?\x0f\x10\xaa\x93"\xe3\xfd?\xe5gx\xb2Vy\xfe?[\xe9m\x8dn\x0f\xff?\x87\xf0\xfc$j\xa5\xff?"\x07\xcb\xbc\xa4\x1d' Setting it to decode and ignore all the non-UTF-8/UTF-16 characters doesn't help much, but what I'm wondering is if the right thing to do is only parse up to the first space, or only parse the first (in this case) 212 characters. I am not 100% sure but my suspicion is that the buffer internal to the simulation code may be allocated to a different length than the buffer that gets written out or something, and that these could potentially be uninitialized memory. What we may want to do is modify the code in general, but I think here the safest thing to do would be to either add a try/except block so that it fails on decoding and just stores the raw bytes, or skip this parameter. If you wanted to modify the data file (which I am always loathe to do) you could set the attribute to be just "Fe,Mg,O,S,Zn,Sr,Y,Ba,Eu,Metals," . Let me know what you think, and we can try taking it from there. -Matt On Tue, Mar 29, 2022 at 7:45 PM HyeonYong Kim <gusdyd398@snu.ac.kr> wrote:

Hi,

I'm writing this since I got a similar problem loading data. my output data is the halo catalogs from hop halo finder, and the simulation code is Gear(this is a chemo-dynamical tree SPH code based on Gadget)

When I try to load the file, there is an error like this " yt.load("halo_catalogs/snapshot_0565/snapshot_0565.0.h5") --> utf-8' codec can't decode byte 0x86 in position 216: invalid start byte "

I know that the cause of this error is the encoding type, but I don't know how to handle this in yt. I tried to load the file in HDFView and saved it to hdf5 format, but there is another error - 'Could not determine input format from ~'

Is there any way to load this file? I'll attach the google drive link to get this file. https://drive.google.com/file/d/1lWEfsPpBjsSqOoXNNAiP2E3-YGHAuM3K/view?usp=s...

Thanks, HyeonYong _______________________________________________ yt-users mailing list -- yt-users@python.org To unsubscribe send an email to yt-users-leave@python.org https://mail.python.org/mailman3/lists/yt-users.python.org/ Member address: matthewturk@gmail.com