Target bytes and src bytes mismatch on box3hr

From: Mishra, Asitav <Asitav.Mishra_at_amd.com>
Date: Tue, 31 May 2022 23:42:39 +0000

[AMD Official Use Only - General]

Hello all,

Sorry for spamming the mail-list with my earlier email. This e-mail corrects the subject line.

I am running a Gadget3 format snap file (Box/3hr) and I get byte mismatch on target vs src byte sizes. A similar post on the mail archive didn't help much since I don't have the same parameters set. I may be missing some configuration input parameters (see attached the Config.sh and parameter file). I am using files that are modified from existing Gadget3 Config and parameter files. The relevant error I get are:

READIC: filenr=0, './/snapdir_044/snap_044.0' contains:
180 READIC: Type 0 (gas): 0 (tot= 0) masstab= 0
181 READIC: Type 1: 2950892 (tot= 191102976) masstab= 0.0138889
182
183 READIC: Reading file `.//snapdir_044/snap_044.0' on task=0 and distribute it to 0 to 6.
184 SNAPSHOT: writing snapshot Reading header => 'HEAD' (264 byte)
185 SNAPSHOT: writing snapshot Reading header => 'HEAD' (264 byte)
186 SNAPSHOT: writing snapshot Reading header => 'HEAD' (264 byte)
187 SNAPSHOT: writing snapshot Reading header => 'HEAD' (264 byte)
188 SNAPSHOT: writing snapshot Reading header => 'HEAD' (264 byte)
189 SNAPSHOT: writing snapshot Reading header => 'HEAD' (264 byte)
190 SNAPSHOT: writing snapshot Reading header => 'HEAD' (264 byte)
191 Code termination on task=32, function type_cast_data(), file src/io/io.cc, line 1389: Strange conversion requested: target_bytes_per_element=24 src_bytes_per_element=23

Any inputs or suggestions would be great.

Thanks,
Asitav





Received on 2022-06-01 01:42:52

This archive was generated by hypermail 2.3.0 : 2022-09-01 14:03:43 CEST