Re: Target bytes and src bytes mismatch on box3hr

From: Mishra, Asitav <Asitav.Mishra_at_amd.com>
Date: Wed, 1 Jun 2022 06:52:00 +0000

[AMD Official Use Only - General]

I am using Gadget4 to run the test case. The config files and parameter files are simply that were used for Gadget3, but have been modified to be consistent with Gadget4.

Asitav

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Tiago Castro <tiagobscastro_at_gmail.com>
Sent: Tuesday, May 31, 2022 11:28:48 PM
To: Gadget General Discussion <gadget-list_at_MPA-Garching.MPG.DE>
Subject: Re: [gadget-list] Target bytes and src bytes mismatch on box3hr

[CAUTION: External Email]
Hi,

  Then it is ok. I got confused because you named the IC file as the snapshot. I believe Gadget will just ignore this if you pass Flag 2. But, again, I am confused, are you using Gadget-3 or 4 to restart the simulation?

Cheers,

Em qua., 1 de jun. de 2022 ās 08:24, Mishra, Asitav <Asitav.Mishra_at_amd.com<mailto:Asitav.Mishra_at_amd.com>> escreveu:

[AMD Official Use Only - General]

Tiago,

Thank you so much for your response. I believe I'm using restart option "2" to run. This is how I run the case:
srun -N $SLURM_NNODES -n $SLURM_NPROCS ./Gadget4 box3_hr.par 2 44

Does that look OK?

Best,
Asitav
________________________________
From: Tiago Castro <tiagobscastro_at_gmail.com<mailto:tiagobscastro_at_gmail.com>>
Sent: Tuesday, May 31, 2022 10:53 PM
To: Gadget General Discussion <gadget-list_at_MPA-Garching.MPG.DE<mailto:gadget-list_at_MPA-Garching.MPG.DE>>
Subject: Re: [gadget-list] Target bytes and src bytes mismatch on box3hr

[CAUTION: External Email]
Hi Asitav,

   I notice that the TimeBegin is still set to the original simulation IC (z=60.0). I am guessing here and hope someone with more experience can help you further. But it seems you are restarting a run from the snapshot that is not at z=60, is it right? If you want to restart from this snapshot, you should fix it to the redshift of the snapshot. In any case, I would recommend you use the Gadget flag to restart from the snapshot file instead of using it as the ICs. I believe the flag is "2", but you can check it by just running Gadget without a parameter file.

Cheers,
---
Em qua., 1 de jun. de 2022 ās 01:44, Mishra, Asitav <Asitav.Mishra_at_amd.com<mailto:Asitav.Mishra_at_amd.com>> escreveu:
[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 08:52:15

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