Grep binary files for ascii text - Revision history

Mrasquin at 01:22, 27 February 2015

2015-02-27T01:22:47Z

Mrasquin at 01:21, 27 February 2015

2015-02-27T01:21:35Z

Mrasquin at 01:20, 27 February 2015

2015-02-27T01:20:12Z

Mrasquin at 01:10, 27 February 2015

2015-02-27T01:10:57Z

Mrasquin at 01:09, 27 February 2015

2015-02-27T01:09:36Z

Mrasquin: Created page with "The phasta files (restart and geombc) includes ascii headers, potentially (but not necessarily) followed by an associated binary block of data. Listing the headers included in yo..."

2015-02-27T00:10:57Z

Created page with "The phasta files (restart and geombc) includes ascii headers, potentially (but not necessarily) followed by an associated binary block of data. Listing the headers included in yo..."

New page

The phasta files (restart and geombc) includes ascii headers, potentially (but not necessarily) followed by an associated binary block of data.
Listing the headers included in your phasta files may be very useful.

@@ Line 29: / Line 29: @@
    grep -a ' : < ' myfile | awk -F @ '{print $1}' | uniq -c
-If you do not want to simplify your life and not type this again and again, you can add the following lines in your .bashrc file which will generate a new linux command named grepfieldsyncio similar to the previous one:
+In order to simplify your life and not type this long command again and again, you can add the following lines in your .bashrc file which will generate a new linux command named grepfieldsyncio:
    vim ~/.bashrc
-−
 Then add
@@ Line 39: / Line 39: @@
+   }
-grepfieldsyncio myfile will now produce the same result as   grep -a ' : < ' myfile | awk -F @ '{print $1}' | uniq -c
+  grepfieldsyncio myfile

@@ Line 12: / Line 12: @@
 Listing the headers included in your phasta files may be very useful. For that purpose, use the following command for instance:
-  grep -a " : < " restart.0.1
+  grep -a ' : < ' restart.0.1
 It will search for the ascii text ' : < ' (space : space < space) in the hybrid ascii - binary file restart.0.1. Note that the key ' : < ' is common to any header included in the geombc or restart files.
@@ Line 33: / Line 33: @@
    vim ~/.bashrc
    grepfieldsyncio() {
        grep -a ' : < ' $1 | awk -F @ '{print $1}' | uniq -c
+   }
-grepfieldsyncio myfile will now produce the same result.
+grepfieldsyncio myfile will now produce the same result as   grep -a ' : < ' myfile | awk -F @ '{print $1}' | uniq -c

@@ Line 12: / Line 12: @@
 Listing the headers included in your phasta files may be very useful. For that purpose, use the following command for instance:
-  grep -a ' : < ' restart.0.1
+  grep -a " : < " restart.0.1
 It will search for the ascii text ' : < ' (space : space < space) in the hybrid ascii - binary file restart.0.1. Note that the key ' : < ' is common to any header included in the geombc or restart files.
-The output will look like this for instance:
+The output of this command for a restart file associated with a single mesh part will look like this for instance:
    byteorder magic number : < 5 > 1
@@ Line 24: / Line 24: @@
    mapping_partid : < 10033 > 1254 1 0
    mapping_vtxid : < 10033 > 1254 1 0

@@ Line 14: / Line 14: @@
   grep -a ' : < ' restart.0.1
-It will search for the ascii text ' : < ' (space : space < space) in the hybrid ascii - binary file restart.0.1. The output will look like this for instance:
+It will search for the ascii text ' : < ' (space : space < space) in the hybrid ascii - binary file restart.0.1. Note that the key ' : < ' is common to any header included in the geombc or restart files.
    byteorder magic number : < 5 > 1

← Older revision		Revision as of 01:09, 27 February 2015
Line 1:		Line 1:
−	The phasta files (restart and geombc) ~~includes~~ ascii headers, potentially (but not necessarily) followed by an associated binary block of data.	+	The phasta files (restart and geombc) include ascii headers, potentially (but not necessarily) followed by an associated binary block of data. A good example is the solution field in a restart file whose header typically looks like this:
−	Listing the headers included in your phasta files may be very useful.	+
		+	solution : < 60193 > 1254 6 0
		+
		+	For the short story,
		+	* if the number between <> is larger than 0, it means this header is followed by a data block in binary format. In this case, this number between <> represents the size of the data block in bytes -1.
		+	* The following numbers are peculiar to the header but for most of the fields in the restart files, the first number after the > sign represents the number of vertices in the considered mesh part (here 1254).
		+	* Then, 6 represents the number of variables per nodes.
		+	* Finally the last number (0 here) is the time step.
		+	Do the math: 1254 vertices * 6 variables per vertex * 8 bytes for a double = 60194.
		+
		+	Listing the headers included in your phasta files may be very useful. For that purpose, use the following command for instance:
		+
		+	grep -a ' : < ' restart.0.1
		+
		+	It will search for the ascii text ' : < ' (space : space < space) in the hybrid ascii - binary file restart.0.1. The output will look like this for instance:
		+
		+	byteorder magic number : < 5 > 1
		+	number of modes : < 0 > 1254
		+	number of variables : < 0 > 6
		+	solution : < 60193 > 1254 6 0
		+	mapping_partid : < 10033 > 1254 1 0
		+	mapping_vtxid : < 10033 > 1254 1 0