For future reference, attached is a snippet of code in C to convert ascii
numbers (integers and doubles) to petsc readable binary vectors.
--
Sajid Ali
Applied Physics
Northwestern University
ascii_to_bin.c
Description: Binary data
I'm attaching the file vector.dat and the file petsc saves (vec_old.dat)
with this email.
Thank You,
Sajid Ali
Applied Physics
Northwestern University
vector.dat
Description: Binary data
vec_old.dat
Description: Binary data
Please email the binary file that you created that is causing you problems.
Barry
> On Dec 5, 2018, at 1:05 PM, Sajid Ali via petsc-users
> wrote:
>
> To clarify :
> The data from xxd -b petsc_output_dat is what I've reordered. The binary dump
> is confusing to read since it
To clarify :
The data from xxd -b petsc_output_dat is what I've reordered. The binary
dump is confusing to read since it contains 6 bytes per line (alongside the
unnecessary ascii conversions) and the numbers start and end in odd places.
I wanted each line to have only one number and copy pasted
It's just a cleaner re-write of the petsc output that I can understand
(which I intend to modify from python in the future). I tried removing the
new line characters but that didn't work either.
Looking at the first line of the binary dump from petsc output :
[sajid at xrm
> On Dec 5, 2018, at 12:40 PM, Sajid Ali
> wrote:
>
> Exactly.
>
> When I run ex10 and inspect it with cat, I get garbage since the data is in
> binary :
>
> [sajid@xrm temp]$ cat vector.dat
> {N?�▒@@ @"@$@&@(@*@,@.@0@1@2@3[sajid@xrm temp]$
>
>
> But doing a binary dump shows the
Exactly.
When I run ex10 and inspect it with cat, I get garbage since the data is in
binary :
[sajid@xrm temp]$ cat vector.dat
{N?�▒@@ @"@$@&@(@*@,@.@0@1@2@3[sajid@xrm temp]$
But doing a binary dump shows the data :
[sajid@xrm temp]$ xxd -b vector.dat
000: 00010010 0011
On Wed, Dec 5, 2018 at 1:27 PM Sajid Ali via petsc-users <
petsc-users@mcs.anl.gov> wrote:
> I have created a file as per the specification as shown below
>
> [sajid@xrm temp]$ cat vector.dat
> 00010010001101001110
> 00010100
>
I have created a file as per the specification as shown below
[sajid@xrm temp]$ cat vector.dat
00010010001101001110
00010100
0011
For future reference, the numbers do look like they're stored as per IEEE
754 64-bit convention.
I don't know what the special characters in the xxd output are but the size
of the file is consistent with 2*int_32+num_elements*dobule_64.
Thank you !
Sajid Ali
Applied Physics
Northwestern
> On Dec 3, 2018, at 1:57 PM, Sajid Ali
> wrote:
>
> Apologies for the error on my part.
>
> Does the vector binary format also work the same way : VEC_FILE_CLASSID (32
> bit int), num_elements (32 bit int) , value of the elements in double
> (num_elements*64 bit double) ?
Yes.
>
Apologies for the error on my part.
Does the vector binary format also work the same way : VEC_FILE_CLASSID
(32 bit int), num_elements (32 bit int) , value of the elements in double
(num_elements*64 bit double) ?
Are the doubles stored in IEEE_754 format ?
On Mon, Dec 3, 2018 at 1:43 PM Smith,
You saved a Vec to the file, not a Mat.
> On Dec 3, 2018, at 1:38 PM, Sajid Ali via petsc-users
> wrote:
>
> Hi,
>
> I ran ex10 from /vec/examples/tutorials and saved the matrix in binary format.
>
> Looking at the matrix in binary using xxd, I see
>
> [sajid@xrm temp]$ xxd -b
Hi,
I ran ex10 from /vec/examples/tutorials and saved the matrix in binary
format.
Looking at the matrix in binary using xxd, I see
[sajid@xrm temp]$ xxd -b vector.dat
000: 00010010 0011 01001110 ..{N..
006: 00010100
14 matches
Mail list logo
