[Nek5000-users] endian problem

[nek5000-users at lists.mcs.anl.gov]

Hi Paul,

Both data and geometry are contained in the restart files. What I meant
was that the binary re2 file was read correctly, but not the restart
files. But yes, I agree, it should not matter -- that's the whole idea
with this if_byte_swap - thing. But anyway, it seems to run with the
slightly older version.

Thanks,

Johan

P.S. Did you see the response from Peake? Looks promising, once I choose
my words carefully in the revised version...

nek5000-users at lists.mcs.anl.gov wrote:
>
> Hi Johan,
>
> are you reading two sets of .f0000 files, one w/ geometry
> and one w/ data?
>
> Do they have different endian characteristics?  (I think
> that shouldn't matter - since endian is determined on a
> file-by-file basis, and the flag set accordingly...)
>
> Paul
>
>
> On Thu, 3 Dec 2009, nek5000-users at lists.mcs.anl.gov wrote:
>
>> Hi,
>>
>> I am trying to start up a job on intrepid now with the newest version of
>> the code, with a resulting endian problem. It seems the code can
>> handle the
>> geometry file correctly but breaks down after reading the restart files
>> with the wrong endian. Is there any new file format that I should be
>> aware of?
>>
>> The output file is attached. Thanks for any tip!
>>
>> Best regards,
>>
>> Johan
>>
>> -- 
>> Johan Ohlsson
>> Department of Mechanics, KTH
>> SE-100 44, Stockholm, Sweden
>> Phone: +46 8 7906876
>> E-mail: johan at mech.kth.se
>>
>>
> _______________________________________________
> Nek5000-users mailing list
> Nek5000-users at lists.mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users


-- 
Johan Ohlsson
Department of Mechanics, KTH
SE-100 44, Stockholm, Sweden
Phone: +46 8 7906876
E-mail: johan at mech.kth.se