ASAsense Binary Table (ABT) format - Bewerkingsoverzicht

Thomas: /* Cli tool for ABT handling */

2025-08-07T09:26:06Z

Cli tool for ABT handling

← Oudere versie		Versie van 7 aug 2025 09:26
Regel 152:		Regel 152:

	* Linux		* Linux
	** [http://asasense.com/abt-binaries/abt-cli-ubuntu-22.04-x86_64.gz Ubuntu 22.04 x86_64]		** [http://asasense.com/abt-binaries/abt-cli-ubuntu-22.04-x86_64.zip Ubuntu 22.04 x86_64]
	** [http://asasense.com/abt-binaries/abt-cli-ubuntu-20.04-x86_64.gz Ubuntu 20.04 x86_64]		** [http://asasense.com/abt-binaries/abt-cli-ubuntu-20.04-x86_64.zip Ubuntu 20.04 x86_64]
	* [http://asasense.com/abt-binaries/abt-win11-x64.zip Windows 11 x64]		* [http://asasense.com/abt-binaries/abt-cli-win11-x64.zip Windows 11 x64]
			The MD5sums of the zipfiles is as follows.
			adcd6a227861bb6b188ef8c5748faae8 abt-cli-ubuntu-20.04-x86_64.zip
			6f4c63cbd7416ead026f170c97b3ab89 abt-cli-ubuntu-22.04-x86_64.zip
			39db54827d2634262d9d666b4262b212 abt-cli-win11-x64.zip

2025-08-05T22:55:22Z

Cli tool for ABT handling

← Oudere versie		Versie van 5 aug 2025 22:55
Regel 150:		Regel 150:
	== Cli tool for ABT handling ==		== Cli tool for ABT handling ==
	To ease the use of the ABT format, a few precompiled binaries are available.		To ease the use of the ABT format, a few precompiled binaries are available.

			* Linux
			** [http://asasense.com/abt-binaries/abt-cli-ubuntu-22.04-x86_64.gz Ubuntu 22.04 x86_64]
			** [http://asasense.com/abt-binaries/abt-cli-ubuntu-20.04-x86_64.gz Ubuntu 20.04 x86_64]
			* [http://asasense.com/abt-binaries/abt-win11-x64.zip Windows 11 x64]

2025-08-05T22:26:24Z

← Oudere versie		Versie van 5 aug 2025 22:26
Regel 123:		Regel 123:
	Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.		Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.

	=== Common Extra Metadata fields ===		== Common Extra Metadata fields ==
	In many ABT files ASAsense uses, the following extra matadata fields will be found		In many ABT files ASAsense uses, the following extra matadata fields will be found
	{\| class="wikitable"		{\| class="wikitable"
Regel 147:		Regel 147:
	\|		\|
	\|}		\|}

			== Cli tool for ABT handling ==
			To ease the use of the ABT format, a few precompiled binaries are available.

2025-08-01T12:40:44Z

Common Extra Metadata fields

← Oudere versie		Versie van 1 aug 2025 12:40
Regel 137:		Regel 137:
	\|Indicates whether the data in the ABT file is sorted by timestamp (column 1)		\|Indicates whether the data in the ABT file is sorted by timestamp (column 1)
	\|-		\|-
	\|		\|frame_width_s
	\|		\|float
	\|		\|NaN
	\|		\|Used to indicate the frame width of one sample (for example the sampling period or spectrogram frame width)
	\|-		\|-
	\|		\|

2025-07-31T14:51:09Z

← Oudere versie		Versie van 31 jul 2025 14:51
Regel 122:		Regel 122:
	\|}		\|}
	Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.		Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.

			=== Common Extra Metadata fields ===
			In many ABT files ASAsense uses, the following extra matadata fields will be found
			{\| class="wikitable"
			\|+
			!Field name
			!Field type
			!Default value
			!Description
			\|-
			\|sorted_by_timestamp
			\|bool
			\|true
			\|Indicates whether the data in the ABT file is sorted by timestamp (column 1)
			\|-
			\|
			\|
			\|
			\|
			\|-
			\|
			\|
			\|
			\|
			\|}

2025-05-12T15:37:55Z

2025-02-05T12:55:54Z

← Oudere versie		Versie van 5 feb 2025 12:55
Regel 30:		Regel 30:
	\|u32		\|u32
	\|0-u32::max		\|0-u32::max
	\|the length of the metadata field (can be 0 is it needs to be skipped)		\|the length of the metadata field (can be 0 if it needs to be skipped)
	\|-		\|-
	\|metadata		\|metadata

2024-10-05T07:37:10Z

← Oudere versie		Versie van 5 okt 2024 07:37
Regel 118:		Regel 118:
	\|"div" should be replaced by any floating point number. The data is then first interpreted as "numtype" (int, uint or float) and then divided by "div". This is mainly useful for storing decimal numbers in integer fields.		\|"div" should be replaced by any floating point number. The data is then first interpreted as "numtype" (int, uint or float) and then divided by "div". This is mainly useful for storing decimal numbers in integer fields.
	\|-		\|-
	\|unix_timestamp		\|unix_timestamp(numtype/div)
	\|Interprets the data as ~~"uint"~~ , but takes into account that it is a unix_timestamp (offset seconds since the Unix Epoch on January 1st, 1970 at UTC)		\|Interprets the data as specified within brackets (so any numtype, with optional divider), but takes into account that it is a unix_timestamp (offset seconds since the Unix Epoch on January 1st, 1970 at UTC)
	\|}		\|}
	Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.		Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.

2024-10-05T07:35:24Z

← Oudere versie		Versie van 5 okt 2024 07:35
Regel 114:		Regel 114:
	\|bool		\|bool
	\|boolean value (0 = false, anything else = true)		\|boolean value (0 = false, anything else = true)
			\|-
			\|numtype/div
			\|"div" should be replaced by any floating point number. The data is then first interpreted as "numtype" (int, uint or float) and then divided by "div". This is mainly useful for storing decimal numbers in integer fields.
			\|-
			\|unix_timestamp
			\|Interprets the data as "uint" , but takes into account that it is a unix_timestamp (offset seconds since the Unix Epoch on January 1st, 1970 at UTC)
	\|}		\|}
	Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.~~<blockquote></blockquote>~~		Other, unknown datatype identifiers, should be treated as opaque binary data (bytes) by the reader.

2024-10-05T07:31:02Z

← Oudere versie		Versie van 5 okt 2024 07:31
Regel 111:		Regel 111:
	\|float		\|float
	\|interpret as floating point data (only possible for 4 or 8 byte fields)		\|interpret as floating point data (only possible for 4 or 8 byte fields)
	\|-
	~~\|numtype/div~~
	\|"div" should be replaced by any floating point number. The data is then first interpreted as "numtype" (int, uint or float) and then divided by "div". This is mainly useful for storing decimal numbers in integer fields.
	\|-		\|-
	\|bool		\|bool